Tech Arsenal 1

home *** CD-ROM | disk | FTP | other *** search

/ Tech Arsenal 1 / Tech Arsenal (Arsenal Computer).ISO / tek-05 / lan2samp.zip / LMU2DOC.INF (.txt) < prev next >

Wrap

OS/2 Help File | 1992-09-10 | 466KB | 21,762 lines

ΓòÉΓòÉΓòÉ 1. Version Notice ΓòÉΓòÉΓòÉ Fourth Edition (October 1992) This edition applies to Version 2 of IBM* LAN Management Utilities/2 and to all subsequent releases and modifications until otherwise indicated in new editions. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. A form for reader's comments appears at the back of this publication. Address your comments to: IBM Corporation Department E02 P.O. Box 12195 Research Triangle Park, North Carolina 27709 U.S.A. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Note: Before using this information and the product it supports, be sure to read the general information in the topic Notices ΓòÉΓòÉΓòÉ 2. Notices ΓòÉΓòÉΓòÉ References in this document to IBM* products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Commercial Relations, IBM Corporation, Purchase, NY 10577. ΓòÉΓòÉΓòÉ 2.1. Trademarks ΓòÉΓòÉΓòÉ The following terms, denoted by an asterisk (*) in this publication, are trademarks of the IBM Corporation in the United States or other countries or both: +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Γöé DATABASE 2 Γöé PC Network Γöé Γöé DB2 Γöé Personal System/2 Γöé Γöé IBM Γöé Presentation Manager Γöé Γöé Micro Channel Γöé PS/2 Γöé Γöé NetView Γöé SAA Γöé Γöé Operating System/2 Γöé Systems Application Architecture Γöé Γöé OS/2 Γöé VTAM Γöé Γöé Γöé XT Γöé +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ The following terms, denoted by a double-asterisk (**) in this publication, are trademarks of other companies: Trademark Company CompuServe CompuServe Incorporated Internetwork packet exchange Novell, Inc. IPX Novell, Inc. MS-DOS Microsoft Corporation NetWare Novell, Inc. NetWare Loadable Module Novell, Inc. NLM Novell, Inc. Novell Novell, Inc. Sequenced packet exchange Novell, Inc. SPX Novell, Inc. ΓòÉΓòÉΓòÉ <hidden> Trademark of IBM ΓòÉΓòÉΓòÉ This term is a trademark of the IBM Corporation. ΓòÉΓòÉΓòÉ 3. Conventions Used in This Document ΓòÉΓòÉΓòÉ This online document uses hypertext, which allows you to obtain additional information on a subject you want to know more about. To see the information, you can select topics from the Table of Contents and the Index, or from a highlighted phrase on a panel. A highlighted phrase appears in a different color from surrounding text. Selecting a highlighted phrase takes you to another section of the document that discusses the subject in greater detail. You can always get back to where you started by pressing the Esc key. You can select highlighted phrases with either the keyboard or a mouse. To use the keyboard, press the Tab key to move from one hypertext phrase to another in a panel, and press Enter to select. With a mouse, double-click on a highlighted phrase to select it. When you have finished viewing this document, you can press F3 to exit. ΓòÉΓòÉΓòÉ 4. About This Book ΓòÉΓòÉΓòÉ The IBM* LAN Management Utilities/2 (LMU/2) is an Operating System/2*- (OS/2*-) based collection of software to aid in the system management of LANs. It allows designated OS/2 workstations to manage other stations on the LAN by: o Obtaining operational and hardware information about the managed stations o Collecting the information in a central repository o Providing automated recovery for selected conditions occurring at the managed stations o Remotely initiating applications at the managed stations. The LMU/2 consists of a command transport system, management applications, and a central repository for data collection. User-written applications can supplement those supplied by IBM. Optionally, LMU/2 commands can be issued through commands from a host, and collected data can be passed to the host. This document contains the external program information necessary to use the LMU/2. ΓòÉΓòÉΓòÉ 4.1. Prerequisite Knowledge ΓòÉΓòÉΓòÉ You should be familiar with LANs (IBM Token-Ring Network, or Ethernet), OS/2, and OS/2 Database Manager. You should be familiar with IBM OS/2 LAN Requester or Novell NetWare Requester for OS/2, as appropriate. For Disk Operating System (DOS) stations that are managed, you should be familiar with the DOS installed on the station, and with the IBM DOS LAN Requester or the Novell NetWare Requester for DOS as appropriate. If you plan to centralize data in a host, you should also be familiar with the host-based database manager, IBM DATABASE 2* (DB2*). If you plan to centralize fault management, familiarity with the IBM NetView* program, the IBM LAN Manager program or IBM LAN Network Manager program, and SNA formats for generic alerts is helpful. Knowledge of the supported IBM personal computers or the supported models of the IBM Personal System/2* (PS/2*) computer is also helpful. ΓòÉΓòÉΓòÉ 4.2. Prerequisite Publications ΓòÉΓòÉΓòÉ Documentation for one of the following operating systems: o IBM Operating System/2 Extended Edition Version 1.3 o IBM Operating System/2 Version 1.3 with IBM Operating System/2 Extended Services o IBM Operating System/2 Version 2.0 with IBM Operating System/2 Extended Services especially including the following publications: o Command Reference o LAN Command Reference o User's Guide o System Administrator's Guide o Problem Determination Guide for the Service Coordinator For a Novell NetWare network: o Novell NetWare Version 3.11 Reference Set, especially the information on NetWare Requesters for DOS and for OS/2 o Novell NetWare Version 3.11 Utilities Reference o Novell NetWare Version 3.11 System Administration ΓòÉΓòÉΓòÉ 4.3. Related Publications ΓòÉΓòÉΓòÉ o IBM Operating System/2 LAN Server Version 1.3 Application Programmer's Reference o IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference o IBM Local Area Network Technical Reference o IBM Operating System/2 Local Area Network Server Version 1.3 Network Administrator's Guide, or later, S33F-9428 o IBM Operating System/2 Local Area Network Server Version 1.3 DOS LAN Requester User's Guide, or later, o System Performance Monitor/2 Reference Manual o IBM Operating System/2 Extended Edition Version 1.3 APPC Programming Reference o IBM Local Area Network Administrator's Guide, GA27-3748 o IBM Local Area Network Support Program User's Guide, S33F-9429 o Novell NetWare Version 3.11 System Messages, for Novell NetWare Requesters (OS/2 or DOS). ΓòÉΓòÉΓòÉ 4.4. How to Get IBM Publications ΓòÉΓòÉΓòÉ Requests for IBM publications should be made to your IBM representative or to the IBM branch office serving your locality. ΓòÉΓòÉΓòÉ 5. Introduction and Requirements ΓòÉΓòÉΓòÉ IBM* LAN Management Utilities/2 (LMU/2) is an Operating System/2*- (OS/2*-) based collection of software that aids LAN administrators in the system management of LANs. This management can be performed at the individual workstation level, the LAN level, and at the enterprise systems level (that is, at the host level of a LAN-attached system). LMU/2 provides the customer with: o A transport method by which LMU/2-provided and user-written management applications can be invoked remotely (OS/2 and Novell NetWare Server stations only). LMU/2 management data can then be sent to a central collection point. o A set of LAN system management applications supplied by IBM. These applications collect and report information necessary to assess and manage the LAN environment, and respond to certain user-specified fault conditions. o Software to maintain an OS/2 database that contains the response information from the management applications supplied by IBM. o A graphical interface that provides: - A display of LAN stations and their status - Panel-driven commands - Visual notification of alert conditions. Terms and Concepts Terms often used when discussing LAN Management Utilities/2 are: Managed System The client computer system that is the target of system management. The OS/2 or NetWare Server managed system receives controlling commands (the LMUCMD commands) from an administrator workstation, executes the requested programs, and sends requested information to the managing system for inclusion in a database. Depending on the options specified on the controlling command, the OS/2 managed system also can relay the console output back to the station that issued the command. Note: A Disk Operating System (DOS) managed system cannot receive controlling commands; it can, however, send information to a managing system for inclusion in a database. Managing System The computer system that monitors the status of its client (managed) systems and optionally is the repository of the OS/2 database containing system management application response information. This system is the focal point of LMU/2 activity. A managing system can also be managed by another managing system. Database System A managing system that also maintains an LMU/2 database (the repository for collected information). This is more usually referred to as a managing system with database. Administrator Workstation The computer system that issues the controlling commands (LMUCMD) to the managed systems. Fault Management System The system that handles generic alerts originating from workstations. There are two parts to the fault management system: fault reporters, and a fault manager. Fault reporter In a managed, managing, or administrator system, the LMU/2 component that generates generic alerts arising from fault conditions in the workstation and that routes those alerts to the fault manager system. The fault reporter is included automatically in every managed system. The alerts are generated at the request of LMU/2 application programs and OS/2 subsystems in the workstation. In an OS/2 workstation, the alerts can also be generated at the request of user-written application programs that conform to the fault management application program interface (API) that is described in Alert Generation and Routing. In a DOS workstation, alerts can be generated through the use of the LMU/2 alert component for DOS, either through a user-written batch file or from the DOS command line. Fault manager The computer system that intercepts and responds to the alerts. It searches a user-defined table to determine for each alert whether to perform automated recovery, thresholding, and notification to other network management software. An OS/2 station on the network can exercise a combination of LMU/2 functions, provided it meets the requirements for each function and contains or has access to all software and files necessary for each function. o It can be both managing and managed; that is, the system manages itself as well as managing other systems. o Whether managed, managing, or both, it can also be the administrator workstation, fault manager, or both. ΓòÉΓòÉΓòÉ 5.1. Overview ΓòÉΓòÉΓòÉ LMU/2 programs are started and driven through command line interfaces, or through a graphical user interface to the command line. LMU/2 takes advantage of the client-server protocol to provide the command and data transport. This transport is used to direct the managed systems to run the system management applications. The transport also is used to send the application data back to the database system. The LMU/2 commands can be initiated from an IBM NetView host. A portion of the database system interfaces with the OS/2 Database Manager to create and maintain a relational database containing the system management application data. This database can then be the target of Structured Query Language (SQL) query programs. The supporting software that interfaces with the OS/2 Database Manager and maintains the database can be run remotely from your primary managing system. To centralize data at a multiple virtual storage (MVS) host, the LMU/2 database data can be exported, converted to host integration exchange format (IXF), and uploaded to the host for inclusion in an IBM DATABASE 2* (DB2*) database. Management Applications (OS/2), Management Applications (DOS), and Management Applications (Novell NetWare Server), describe the IBM-supplied system management applications; LAN Management Utilities/2 Database Tables describes the database tables created and maintained for these applications. The actual location of the LMU/2 modules and files is left entirely to the LAN administrator. The primary requirement is that the managed and managing computers have access to the disk (or logical disk) that houses the applications (transport or system management) to be run in those computers. ΓòÉΓòÉΓòÉ 5.1.1. LMU/2 System Needs and Functions ΓòÉΓòÉΓòÉ This section discusses the requirements and functions for the LMU/2 stations. To see the workstation discussion for a particular system, double-click on a highlighted phrase or tab the cursor to a highlighted phrase and press Enter. In the station discussions, the term "IBM" followed by an LMU/2 system type, as in "IBM managing system", is used to designate a workstation that is running the necessary IBM OS/2 LAN Requester or LAN Server and the appropriate LMU/2 software. Similarly, the term "Novell" followed by an LMU/2 system type, as in "Novell managed system", is used to designate a workstation that is running the necessary Novell NetWare Requester or Server and is running the appropriate LMU/2 software. The term "IBM-Novell" followed by an LMU/2 system type, as in "IBM-Novell managing system", is used to designate a workstation that is running both the IBM OS/2 LAN Requester and the Novell NetWare Requester for OS/2, and is running the appropriate LMU/2 software. Administrator Workstation Managing System Managed System Fault Manager Fault Reporter Communication Between Systems LMU/2 applications in an IBM LMU/2 system use the NETBIOS protocol to communicate with LMU/2 applications in another IBM LMU/2 system. LMU/2 applications in a Novell LMU/2 system use integrated packet exchange (IPX) and sequenced packet exchange (SPX) protocols to communicate with LMU/2 applications in another Novell LMU/2 system. In an IBM-Novell LMU/2 system, IBM communicates with IBM, and Novell communicates with Novell. ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé IBM Γöé <-------------> Γöé IBM Γöé Γöé IBM Γöé <-------------> Γöé IBM Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé------Γöé ΓöéNOVELLΓöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé IBM Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé------Γöé ΓöéNOVELLΓöé <-------------> ΓöéNOVELLΓöé ΓöéNOVELLΓöé <-------------> ΓöéNOVELLΓöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé IBM Γöé <-------------> Γöé IBM Γöé Γöé------Γöé Γöé------Γöé ΓöéNOVELLΓöé <-------------> ΓöéNOVELLΓöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ 5.1.1.1. Administrator Workstation ΓòÉΓòÉΓòÉ The station that serves as an administrator workstation must have: o One of the following programs executing: - The IBM OS/2 LAN Requester program - The Novell NetWare Requester for OS/2 program - Both the IBM OS/2 LAN Requester program and the Novell NetWare Requester for OS/2 program - The IBM OS/2 LAN Server program. o An appropriate logon or login: - For an OS/2 LAN Requester or LAN Server, a userid that is logged on as a domain administrator (SYSADM) to an IBM LAN - For a NetWare Requester or OS/2, a userid that is logged in to a NetWare Server as a supervisor equivalent o Access to the LMU/2 remote-execution software (LMUCMD.EXE, for example). The administrator workstation performs the following function: o Issues LMUCMD commands to instruct non-DOS managed systems to execute management or user applications An IBM administrator workstation issues commands to IBM managed systems. A Novell administrator workstation issues commands to Novell managed systems. An IBM-Novell administrator workstation can issue commands to both types of managed systems. The administrator workstation system is usually in the same station as a managing or managed system, which gives it the ability to direct locally generated alerts to the fault management system (fault reporting), for resolution or forwarding to a central network managing location. If the station containing the administrator workstation system does not also contain a managing or managed system, it is recommended that the fault reporter function be included in the station. ΓòÉΓòÉΓòÉ 5.1.1.2. Managing System ΓòÉΓòÉΓòÉ A station that serves as a managing system must be running one of the following programs, and must be running the LMU/2 managing software (LMUSRV). o The IBM OS/2 LAN Requester program o The Novell NetWare Requester for OS/2 program o Both the IBM OS/2 LAN Requester program and the Novell NetWare Requester for OS/2 program o The IBM OS/2 LAN Server program. In general, a managing system performs the following functions: o Forwards to managed systems the LMUCMD broadcast commands initiated from an administrator workstation o Receives configuration and performance information from managed systems and records the data in the LMU/2 database (if it maintains an LMU/2 database) o Monitors "heartbeats" from the managed systems. If the managing system maintains an LMU/2 database, the station must be logged on either as a local administrator (authorization type DBADM) or as a domain administrator (authorization type SYSADM), using the same userid as when the database was created. An IBM managing system manages only workstations that have either the IBM LAN Requester (OS/2 or DOS) or the IBM OS/2 LAN Server running. A Novell managing system manages only workstations that have either the Novell NetWare Requester (OS/2 or DOS) or the Novell NetWare Server running. An IBM-Novell managing system can manage workstations that have the IBM LAN Requester (OS/2 or DOS) running, the Novell NetWare Requester (OS/2 or DOS) running, or both. An IBM-Novell managing system also can manage workstations that have the IBM OS/2 LAN Server or the Novell NetWare Server running. ΓòÉΓòÉΓòÉ 5.1.1.3. Managed System ΓòÉΓòÉΓòÉ A managed system may be an OS/2 station, a DOS station, or a NetWare Server station. Note that a DOS managed system cannot receive controlling commands. For station requirements and managed system functions, tab the cursor to one of the highlighted phrases and double-click or press Enter. ΓòÉΓòÉΓòÉ 5.1.1.3.1. OS/2 Station ΓòÉΓòÉΓòÉ An OS/2 station that is a managed system must be running one of the following programs, must be running the LMU/2 LMUCLI software, and must have access to the LMU/2 management applications. o The IBM OS/2 LAN Requester program o The Novell NetWare Requester for OS/2 program o Both the IBM OS/2 LAN Requester program and the Novell NetWare Requester for OS/2 program o The IBM OS/2 LAN Server program. In general, an OS/2 managed system performs the following functions: o Executes management applications as directed by LMUCMD commands received from an administrator workstation. Management applications include such things as collecting vital product data or performance data about the managed station and sending it back to a managing system for inclusion in the LMU/2 database. o Executes, as directed by LMUCMD commands received from an administrator workstation, any command that can be invoked at the OS/2 command prompt that does not require a user response. o Issues periodic "heartbeats" to the managing system to indicate that the LMUCLI software in the managed station is still functioning. An IBM Managed system can be managed by an IBM or IBM-Novell managing system. A Novell managed system can be managed by a Novell or IBM-Novell managing system. An IBM-Novell managing system can be managed by an IBM, Novell, or IBM-Novell managing system. ΓòÉΓòÉΓòÉ 5.1.1.3.2. DOS Station ΓòÉΓòÉΓòÉ A DOS station that is a managed system must be running one of the following programs, and must have access to the DOS LMU/2 management applications. o IBM DOS LAN Requester program o Novell NetWare Requester for DOS program o Both the IBM DOS LAN Requester program and the Novell NetWare Requester for DOS program. In general, a DOS managed system performs the following functions: o Collects configuration information as directed by operator request from the DOS command line, from AUTOEXEC.BAT, or from any other DOS program vehicle that can issue line commands. A DOS station cannot serve as the target of LMUCMD commands. o Sends the collected information to a managing system for inclusion in the LMU/2 database. o Issues an initial "heartbeat" to the managing system to indicate the presence of the DOS workstation on the LAN. An IBM Managed system can be managed by an IBM or IBM-Novell managing system. A Novell managed system can be managed by a Novell or IBM-Novell managing system. An IBM-Novell managing system can be managed by an IBM, Novell, or IBM-Novell managing system. ΓòÉΓòÉΓòÉ 5.1.1.3.3. NetWare Server Station ΓòÉΓòÉΓòÉ A Novell NetWare Server that is a managed system must have Novell NetWare Version 3.11 executing, must be running the LMU/2 LMUCLI software, and must have access to the LMU/2 management applications for NetWare. In general, a NetWare Server managed system performs the following functions: o Executes management applications as directed by remote-execution commands received from an administrator workstation. Management applications include such things as collecting vital product data or performance data about the managed station and sending it back to a managing system for inclusion in the LMU/2 database. o Executes, as directed by remote-execution commands received from an administrator workstation, any command that can be invoked from the system console that does not require a user response. o Issues periodic "heartbeats" to the managing system to indicate that the client software in the managed station is still functioning. A NetWare Server managed system can be managed by a Novell or IBM-Novell managing system. ΓòÉΓòÉΓòÉ 5.1.1.4. Fault Manager ΓòÉΓòÉΓòÉ The station that contains the fault manager system must have one of the following programs running, unless the fault manager is acting as the LAN Network Manager (LNM) user exit routine. o The IBM OS/2 LAN Requester program o The Novell NetWare Requester for OS/2 program o Both the IBM OS/2 LAN Requester program and the Novell NetWare Requester for OS/2 program o The IBM OS/2 LAN Server program. The IBM OS/2 LAN Server and the Novell Requester in the same station is not a supported configuration. If the fault manager is to perform automated recovery for alerts, the station must also be an administrator workstation. Note: If the LMU/2 fault manager is enabled as the LNM user exit routine (AUEDRIVR.DLL is specified in LNM as the user exit): 1. The intercept portion of the fault manager (AUECATCH) must not be started in the LNM workstation. 2. Because LNM receives alerts through its Alert Transport Service (ATS), LNM ordinarily does not receive LMU/2 alerts, and therefore does not pass LMU/2 alerts to the fault manager. To enable the fault manager to process LMU/2 alerts when serving as the LNM user exit routine, use a different station as the focal point for LMU/2 alerts, as follows: a. Specify the LNM adapter address as the FM_FORWARDING_ADDR in the LMU.INI file of the non-LNM station. b. Start AUECATCH in the non-LNM station, with the option to forward alerts to a LAN management address (AUECATCH 2). c. In the LMU.INI file in stations running the fault reporter component, identify the station running AUECATCH as the fault manager station (FAULT_MANAGER). Do not identify the LNM station as the fault manager. In this way, LMU/2 alerts are directed to the station running AUECATCH, which can then forward the alerts to the LNM through the Alert Transport Service. The native fault manager (that is, the intercept and response components together, not acting as the LNM user exit routine) performs the following functions: o Receives generic alerts from LMU/2 applications and OS/2 subsystems in the client computers (if the application programs are enabled to send alerts to the fault manager). o Compares alerts received against those defined by the user in the alerts table file. If the alert matches a table entry, the fault manager: - Determines if the notification threshold has been reached and, if so, forwards the alert to IBM NetView* or to a LAN management functional address, such as the IBM LAN Network Manager. - Determines if the automation threshold has been reached and, if so, uses the command transport mechanism of LMU/2 to invoke the specified recovery procedure at the appropriate target workstation. If the alert does not match a table entry, or the table is unavailable, or the alert is a hardware alert: - Forwards the alert to IBM NetView or to the IBM LAN Network Manager. The fault manager acting as the LNM user exit routine performs the following functions: o Examines any alert passed to it by the LNM, which receives alerts through its Alert Transport Service (ATS). If the alert matches a table entry, the fault manager: - Determines if the notification threshold has been reached and, if so, returns a "pass" indication to the LNM, notifying the LNM to forward the alert. If the notification threshold has not been reached, the fault manager returns a "block" indication, notifying the LNM not to forward the alert. - Determines if the automation threshold has been reached and, if so, uses the command transport mechanism to invoke the specified recovery procedure at the appropriate target workstation. If the alert is a hardware alert, the alert does not match a table entry, or the table is unavailable: - Returns a "pass" indication to the LNM, notifying the LNM to forward the alert. An IBM fault manager receives alerts only from IBM fault reporters. A Novell fault manager receives alerts only from Novell fault reporters. An IBM-Novell fault manager receives alerts from both types of fault reporters. Note: If the LAN Network Manager is on the network, it is strongly recommended that the LMU/2 fault manager be enabled as the LAN Network Manager user exit routine. If the LAN Network Manager is in the same station as the fault manager, the fault manager must be enabled as the LAN Network Manager user exit routine. ΓòÉΓòÉΓòÉ 5.1.1.5. Fault Reporter ΓòÉΓòÉΓòÉ The fault reporter system is that portion of the fault management software that routes generated generic alerts to the fault manager. The fault reporter should be installed and enabled in every LMU/2 station that may need to generate generic alerts. This applies particularly to any station that functions as an LMU/2 managed system, managing system, or administrator workstation. The fault reporter system is enabled automatically in every LMU/2 OS/2 managed system. A fault-reporter-only station is a station that does not execute LMU/2 commands and is not to be the target of LMUCMD commands but does route generated alerts to the fault manager. This station must have one of these requester programs executing: o IBM OS/2 LAN Requester o IBM DOS LAN Requester o Novell NetWare Requester for OS/2 o Novell NetWare Requester for DOS and must be executing the alert-routing portion of the fault management software (for OS/2 stations: AUEUSRGA, AUEPITCH, and possibly AUEREXGA; for DOS stations: AUEDOSAL). The fault-reporter-only station performs the following function: o Directs locally generated alerts to the fault manager for resolution or forwarding to a central network managing location. For OS/2 stations, the locally generated alerts are from LMU/2 application programs and OS/2 subsystems in the workstation, and from user-written applications that conform to the application program interface (API) described in Alert Generation and Routing. For DOS stations, the alerts are generated through the use of AUEDOSAL, either in a user-written batch file or from the DOS command line. ΓòÉΓòÉΓòÉ 5.1.2. Contents of the LAN Management Utilities/2 Package ΓòÉΓòÉΓòÉ The LAN Management Utilities/2 package includes: o The IBM LAN Management Utilities/2 program diskettes 1-3 (3.5-inch 1.44 MB). These diskettes contain this softcopy documentation, OS/2 programs and files in packed format, and (on diskette 3) DOS and NLM programs and files in unpacked format o This softcopy documentation on LMU/2 diskette 1 (3.5-inch 1.44 MB). o The IBM LAN Management Utilities/2 General Information manual, GA27-3961. o Memos to the user, including instructions on viewing the documentation. ΓòÉΓòÉΓòÉ 5.2. Hardware and Software Requirements ΓòÉΓòÉΓòÉ This topic details the hardware and software requirements for the LAN Management Utilities/2. ΓòÉΓòÉΓòÉ 5.2.1. Software Requirements ΓòÉΓòÉΓòÉ Managing System o IBM Operating System/2 Version 1.3 or later o IBM OS/2 REXX o IBM OS/2 LAN Requester 1.3.1 or later, or Novell NetWare Requester for OS/2, or both o IBM OS/2 Communications Manager, if the managing system is to communicate with a host o IBM OS/2 Database Manager, if the managing system is to maintain the LMU/2 database Managed System (OS/2) o IBM Operating System/2 Version 1.3 or later o IBM OS/2 REXX o IBM OS/2 LAN Requester 1.3.1 or later, or Novell NetWare Requester for OS/2, or both Managed System (NetWare Server) o Novell NetWare 3.11 Managed System (DOS) o IBM Disk Operating System Version 3.3 or later o IBM DOS LAN Requester 1.3 or later and IBM Local Area Network Support Program 1.2, or Novell NetWare Requester for DOS, or both. Administrator Workstation o IBM Operating System/2 Version 1.3 or later o IBM OS/2 REXX o IBM OS/2 LAN Requester 1.3.1 or later, or Novell NetWare Requester for OS/2, or both Fault Manager o IBM Operating System/2 Version 1.3 or later o IBM OS/2 REXX o IBM OS/2 LAN Requester 1.3.1 or later, or Novell NetWare Requester for OS/2, or both o IBM OS/2 Communications Manager, if the fault manager is to forward alerts to IBM NetView or to a LAN management functional address, such as the IBM LAN Network Manager. Fault Reporter Only (OS/2) o IBM Operating System/2 Version 1.3 or later o IBM OS/2 LAN Requester 1.3.1 or later, or Novell NetWare Requester for OS/2, or both Fault Reporter Only (DOS) o IBM Disk Operating System Version 3.3 or later o IBM DOS LAN Requester 1.3 or later and IBM Local Area Network Support Program 1.2, or Novell NetWare Requester for DOS, or both. The IBM System Performance Monitor/2 (SPM/2) is required in any OS/2 station that is to execute certain LMU/2 performance applications. The version of SPM/2 required depends on the version of OS/2 in the workstation. ΓòÉΓòÉΓòÉ 5.2.2. Hardware Requirements ΓòÉΓòÉΓòÉ OS/2 Station: For an OS/2 station, any personal computer or IBM Personal System/2* (PS/2*) computer or equivalent that is supported by the IBM OS/2 operating system used and that has: o A Token-Ring Network or Ethernet adapter that is supported by the IBM OS/2 operating system used. o A 3.5-inch 1.44 MB diskette drive on the computer used to install the LMU/2 software. o Approximately 4 MB of disk space on the drive that contains the LMU/2 software. This number assumes a shared disk on the network and includes the programs for DOS stations. Any log files used on that same drive will increase the disk space requirement. DOS Station: For a DOS station, any personal computer or IBM PS/2 computer or equivalent that is supported by the IBM DOS operating system used and that has: o A Token-Ring Network or Ethernet adapter that is supported by the IBM DOS operating system used o A 3.5-inch 1.44 MB diskette drive on any computer used to copy software from the LMU/2 diskette. o Approximately 420 KB of disk space for the LMU/2 DOS programs, if copied to the DOS station`s computer. If the LMU/2 software is installed on a shared disk accessible to the DOS station, there is no disk space requirement in the DOS station for the LMU/2 DOS programs. However, disk space is required for the LMU/2 message log file that will be placed in the C: drive root directory of the DOS station. The amount of disk space required depends on how often you empty the log file. ΓòÉΓòÉΓòÉ 5.3. Running System Management Applications ΓòÉΓòÉΓòÉ There are two ways to invoke the system management applications: remotely and locally. ΓòÉΓòÉΓòÉ 5.3.1. Remote Command Execution (OS/2 Stations or NetWare Servers Only) ΓòÉΓòÉΓòÉ From an administrator workstation, issue the LMUCMD command to direct an OS/2 managed computer to run a system management application program (such as QUERYVPD or PERFCAP). The LMUCMD command accepts as input: o The identity of a target (managed) computer, or of a range of target computers. For IBM managed systems, this is the computer name; for Novell managed systems, this is the internetwork address, the login userid, or a server name. o The name of the command or program to be run at the managed computer, along with any associated parameters. The command can be another LMUCMD command directed at another target computer. The command must not require a user response. Remote execution allows you to write an unattended automation facility to perform: o Workstation diagnostics and associated recovery o Time-triggered functions. Refer to the topic LMUCMD for a full description of the LMUCMD command interface. ΓòÉΓòÉΓòÉ 5.3.2. Local Command Execution ΓòÉΓòÉΓòÉ From an OS/2 workstation (does not have to be a managed station): Execute the LMU/2 management applications (such as QUERYVPD or PERFCAP) from the OS/2 command line in an active OS/2 session (window), or through any program vehicle that can issue line commands (user programs, REXX programs, STARTUP.CMD, and so forth). The destination of the management application output is dictated by the program being run and the command operands to which it reacts. Refer to Management Applications (OS/2) for a full description of the OS/2 management applications supplied by IBM. From a managed DOS computer: Execute the DOS application (such as QDOSVPD) from the DOS command line or through any program vehicle that can issue line commands (user programs, system or user login script, AUTOEXEC.BAT, and so forth). The destination of the command output is dictated by the command operands given. Refer to Management Applications (DOS) for a full description of the DOS management applications supplied by IBM. From a managed NetWare Server computer: Load the LMU/2 management application (such as QUERYVPD.NLM) from the system console. The destination of the management application output is dictated by the program being run and the command operands to which it reacts. Refer to Management Applications (Novell NetWare Server), for a full description of the management applications supplied by IBM for a NetWare Server. ΓòÉΓòÉΓòÉ 5.4. Managing from a Host ΓòÉΓòÉΓòÉ The Communications Manager component of Extended Services for OS/2 has a function known as Remote Operations Service (ROPS). ROPS allows you to enter an OS/2 command from the NCCF component of IBM NetView, and have the standard output (STDOUT) of that command piped back to your NCCF display. The OS/2 command entered can be an LMU/2 command, such as QUERYVPD or LMUCMD. The computer that is the ROPS target of your OS/2 command must have an SSCP-PU session with the host. To reach a target that does not have an SSCP-PU session with the host, from NCCF send an LMUCMD command to an LMU/2 administrator workstation that does have an SSCP-PU session with the host. The LMUCMD command is of the format LMUCMD mged command-string where mged is the name of the intended managed station, and command-string is the command you want executed at the intended managed station (see topic LMUCMD for more details on the format and function of the LMUCMD command). The administrator workstation that is the ROPS target routes the LMUCMD command down to the managed station. The output goes from the managed station to the administrator workstation to NCCF. This takes a while; you may want to consider putting the output in a file at the administrator workstation (use redirection in the LMUCMD command-string) and then transferring it later to a host, where it can be browsed at your leisure. ΓòÉΓòÉΓòÉ 6. Installation and Customization ΓòÉΓòÉΓòÉ LAN Management Utilities/2 (LMU/2) is designed to run in the OS/2 and Novell NetWare environments, with some LMU/2 function on DOS stations. An OS/2 LAN Requester station or NetWare Requester for OS/2 station can perform any combination of LMU/2 functions if the appropriate software is installed and available, and if the station has been customized for the functions. A Novell NetWare Server can be an LMU/2 managed system if the appropriate software is installed and available, and if the NetWare Server has been customized for the function. An installation program, LMUINST, runs on an OS/2 station and automatically installs the LMU/2 programs and files on the station or on a shared disk in a network file server. If the shared disk is on an IBM OS/2 LAN Server, only IBM OS/2 LAN Requesters and IBM DOS LAN Requesters can access the shared disk; if the shared disk is on a Novell NetWare file server, only NetWare Requesters (OS/2 or DOS) can access the shared disk. An OS/2 workstation must be able to access the disk where the LMU/2 programs and files reside, or must have the necessary programs and files installed on the workstation. A DOS workstation must be able to access the disk where the LMU/2 programs and files reside, or must have the necessary programs and files copied to the workstation. Each station in the network that will run any LMU/2 function must be customized for LMU/2. Return to the Table of Contents and select the installation and customization topics that relate to the stations in your network. ΓòÉΓòÉΓòÉ 6.1. Installation for OS/2 Stations ΓòÉΓòÉΓòÉ Note: This topic applies to a workstation running an IBM OS/2 LAN Requester or Novell NetWare Requester for OS/2 or both. For simplicity, an automated installation routine (LMUINST) has been provided that runs on an OS/2 station and installs all LMU/2 software onto an OS/2 station or onto a shared disk. If the disk receiving the software is a shared disk, all the LMU/2 software will be available to all stations that have access to that disk. If you do not choose to use a shared disk, run the installation program on every OS/2 station that will execute any LMU/2 programs. See Running LMUINST. If a DOS station that will be running LMU/2 programs does not have access to a shared disk, see Installation for a DOS Station. For a NetWare Server that will be running LMU/2 programs or maintaining the shared disk for NetWare Requesters, see Installation for a NetWare Server. ΓòÉΓòÉΓòÉ 6.1.1. Running LMUINST ΓòÉΓòÉΓòÉ LMUINST runs on an OS/2 computer only. ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUINST ΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ALL ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö┤ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ IBM ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇ /Tx ΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ NETWARE ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ MANAGING ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ GUI ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ DOC ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ALL Install all LMU/2 programs and documentation IBM Install LMU/2 programs for IBM LAN Server/Requester NETWARE Install LMU/2 programs for Novell NetWare MANAGING Install LMU/2 Managing System programs GUI Install LMU/2 Graphical User Interface programs DOC Install LMU/2 documentation /Tx - x indicates the target drive on which the code is to be installed. If not specified, defaults to boot drive. EXAMPLE: A:\LMU2\LMUINST /TD ALL - will install LMU2 files from A:\LMU2 subdirectory to D:\LMU2 subdirectory To install the LAN Management Utilities/2: 1. Insert the LAN Management Utilities/2 diskette 1 into the A: drive of the computer. 2. Enter the A:LMUINST command and desired parameters at the OS/2 prompt. Parameters: o all - Copy all the LMU/2 programs and files (for OS/2, Novell, and DOS systems), the graphical user interface, and the online documentation to the target disk. o ibm - Copy only the LMU/2 programs and files for an IBM LAN Server/Requester environment (OS/2 and DOS) to the target disk. The programs and files for a managing system, the graphical user interface, and the online documentation are not copied unless those parameters are also specified. Programs and files for Novell NetWare Requesters and Servers are not copied. o netware - Copy only the LMU/2 programs and files for a Novell NetWare environment to the target disk. The programs and files for a managing system, the graphical user interface, and the online documentation are not copied unless those parameters are also specified. Programs and files for IBM LAN Servers and LAN Requesters are not copied. o managing - Copy only the programs and files for a managing system to the target disk. o gui - Copy only the graphical user interface and the online documentation to the target disk (the graphical user interface links into the online documentation). o doc - Copy only the online documentation to the target disk. o /Td - Specify the target drive that is to receive the LMU/2 software, where d is a letter that identifies the target drive. The drive may be a shared drive. If the /Td parameter is not specified, the boot drive of the computer is used. If managing or gui is specified: either ibm or netware should be specified also, unless one or both environments have been installed previously with LMU/2 2.0 LMUINST. The LMUINST program copies all specified files to whatever drive you specified, which may be mapped or aliased. After you install the LMU/2 software, you must customize every station (DOS, OS/2, or NetWare Server) that will use any of the software. See Customizing OS/2 Stations, Customizing a DOS Station, and Customizing a Novell NetWare Server, as appropriate. ΓòÉΓòÉΓòÉ 6.2. Customizing OS/2 Stations ΓòÉΓòÉΓòÉ Note: This topic applies to a workstation running an IBM LAN Requester or Novell NetWare Requester or both. After the LMU/2 software has been installed on each station or on a shared disk, the next step is to create or update required files on each station. The LMU/2 customization program, LMUCUST, automates most of these tasks for you on OS/2 stations. LMUCUST does not, however, modify system files such as OS/2 Communications Manager profiles or DOS station DOSLAN.INI files. Therefore, after you have followed the instructions for customizing IBM OS/2 LAN Requester stations (see Customizing the Fault Manager and All OS/2 Stations), be sure to review all of Preparing the Environment (from topic Preparing the Environment to Handling Generic Alerts) to make certain you have performed all necessary tasks in each station. To customize DOS stations, go to Customizing a DOS Station. To customize Novell NetWare Servers, go to Customizing a Novell NetWare Server. ΓòÉΓòÉΓòÉ 6.2.1. Customizing the Fault Manager ΓòÉΓòÉΓòÉ In addition to performing the customization steps required for all OS/2 stations, for each fault manager station you must create an alerts table that identifies the generic alerts you want the fault manager to process. The user-written alerts table is described in User-Defined Table. If the fault manager is to function as the IBM LAN Network Manager alerts user exit routine, see Special Considerations for Fault Manager and see the fault manager notes in the Running LMUCUST section. ΓòÉΓòÉΓòÉ 6.2.2. All OS/2 Stations ΓòÉΓòÉΓòÉ You should run LMUCUST in each OS/2 station in which LMU/2 programs are to execute. If you prepare the necessary .CTL and .CFG or .DAT input files before running LMUCUST, LMUCUST automatically creates the required LMU.INI file and the optional USERVPD.DAT file for the station in which it is running, and places the files in the required locations in the station (see About Creating LMU.INI and Creating USERVPD.DAT for instructions). Otherwise, you must create the station's LMU.INI file yourself and, optionally, the USERVPD.DAT file as described in Preparing the Environment. LMUCUST also copies necessary files to required locations, updates the station CONFIG.SYS file, and, if needed, updates the STARTUP.CMD file. ΓòÉΓòÉΓòÉ 6.2.2.1. About Creating LMU.INI ΓòÉΓòÉΓòÉ An LMU.INI file is required in each OS/2 station before any LMU/2 programs can execute in the station. The LMU.INI file specifies such items for the station as: o The identity of the managing station o The identity of the LMU/2 database station o The identity of the fault manager station or focal point o The location of the fault management user-written alerts table o The location of the LMU/2 database BIND statements o The location of the LMU/2 message log o The location of the LMU/2 change log o The LMU/2 pulse rate ("heartbeat" rate) o The threshold specifications for the performance commands o The location of other key LMU/2 files. In order for LMUCUST to create the LMU.INI file, you must provide a control file that contains the variables for the station. A sample control file, LMUCTL.SMP, is included with the LMU/2 software. Copy the sample control file, edit it, and name it as described below. See Specifying LMU.INI Variables for the contents of the control file. LMUCUST places the created LMU.INI file in the root directory of the station's OS/2 boot drive. The control file to be used for the workstation must be in the directory from which LMUCUST is executing (that is, the directory that contains the installed LMU/2 software), and must be one of the following: Global control file Use this for all the stations in the network that have the same LMU.INI parameter values (the same managing system, database machine, pulse rate, and so forth). Name this file LMU.CTL and place it in the directory where the LMU/2 software was installed. This can be on a shared disk. Default domain control file Use this for all the stations in an IBM LAN Server domain that have the same LMU.INI parameter values (the same managing system, database machine, pulse rate, and so forth), and the same default domain. The default domain is the domain that was in the workstation's IBMLAN.INI file when the machine was powered on or restarted. Name this file domainname.CTL, where domainname is the name of the default domain, and place it in the directory where the LMU/2 software was installed. This can be on a shared disk. Logon domain control file Use this instead of the default domain file, when you want to assign common LMU.INI parameter values to stations grouped by logon domain instead of by default domain. The logon domain is the domain that the workstation is currently logged into when LMUCUST is run. Name this file domainname.CTL, where domainname is the name of the logon domain, and place it in the directory where the LMU/2 software was installed. This can be on a shared disk. Network name file Use this file for all the OS/2 NetWare Requesters in a Novell NetWare network that have the same LMU.INI parameter values (the same managing system, database machine, pulse rate, and so forth). Name this file networkname.CTL, where networkname is the network number, and place it in the directory where the LMU/2 software was installed. This can be on a shared disk. Node address file Use this file if the station is a Novell NetWare Requester for OS/2 and needs a different parameter value from the other Novell NetWare Requesters in the Novell network. Name this file nodeaddress.CTL, where nodeaddress is the rightmost 8 characters of the internetwork address for the station, and place it in the directory where the LMU/2 software was installed. This can be on a shared disk. Station control file Use this file if the station is an IBM LAN Requester station logged into an IBM LAN Server and needs a different parameter value from the other stations in the domain or network. Name this file computername.CTL, where computername is the computer name specified in the IBMLAN.INI file in the station's computer, and place it in the directory where the LMU/2 software was installed. This can be on a shared disk. Note: For each IBM OS/2 LAN Requester, LMUCUST looks for a .CTL file in the following order, beginning with computername.CTL. computername.CTL default domainname.CTL logon domainname.CTL LMU.CTL If it does not find a control file that matches the station computer name, the default domain name, or the logon domain name, it looks for an LMU.CTL file. For each Novell NetWare Requester for OS/2, LMUCUST looks for a .CTL file in the following order, beginning with nodeaddress.CTL. nodeaddress.CTL networkname.CTL LMU.CTL If it does not find a control file that matches the station node address or the station network number, it looks for an LMU.CTL file. For each station that contains both the IBM OS/2 LAN Requester and the Novell NetWare Requester for OS/2, LMUCUST looks for a .CTL file in the following order, beginning with computername.CTL. computername.CTL nodeaddress.CTL default domainname.CTL logon domainname.CTL networkname.CTL LMU.CTL If it does not find a control file that matches any of these, it looks for an LMU.CTL file. When LMUCUST finds a control file to use, it builds the station's LMU.INI file from that control file and places the LMU.INI file in the root directory of the station's boot drive. If it does not find any of these .CTL files for the station, it copies LMUCTL.SMP to the station's LMU2 directory (on the drive specified by the LMUCUST parameters); you will need to modify LMUCTL.SMP to specify the parameters for the station, and run the LINI program to create the LMU.INI file (see Creating the LMU.INI File in "Preparing the Environment" for details). ΓòÉΓòÉΓòÉ 6.2.2.2. Creating USERVPD.DAT ΓòÉΓòÉΓòÉ The USERVPD.DAT file supplies user-chosen information, such as machine serial numbers and location, to the QUERYVPD and QDOSVPD programs for inclusion in the configuration data sent to the LMU/2 database. The maximum file size is 3500 bytes. The USERVPD.DAT file can be free-form, or it can have user-defined "fields" in it that can be extracted later from the LMU/2 database. To create a USERVPD.DAT file with "fields", see Formatted USERVPD Data. You can create a USERVPD.DAT file at each workstation, using a text editor, or you can create a source file that LMUCUST can use to generate the USERVPD.DAT file for you. To have LMUCUST create the USERVPD.DAT file and place it in the LMU2 directory on the desired drive, do the following: 1. Copy USERVPD.SMP to make one of the following source .CFG or .DAT files for the machine, and place the .CFG or .DAT file in the directory where the LMU/2 software was installed. 2. Modify the source .CFG or .DAT file to contain the values for the computer (the file contains the necessary instructions). Note: In the following discussion, computername is the requester computer name specified in the IBMLAN.INI file in an OS/2 LAN Requester computer. Nodeaddress is the rightmost eight bytes of the internetwork address of a NetWare Requester computer. computername.CFG or nodeaddress.CFG Source file for field-specified USERVPD.DAT file for the machine computername.DAT or nodeaddress.DAT Source file for unformatted USERVPD.DAT file for the machine LMUCUST searches for a source file in the following order (stopping the search at the first find), and places the resulting file on the drive specified in the workstation where LMUCUST is executing: File name Customization operation performed computername.CFG Converted to a field-defined USERVPD.DAT file nodeaddress.CFG Converted to a field-defined USERVPD.DAT file computername.DAT Copied to a USERVPD.DAT file nodeaddress.DAT Copied to a USERVPD.DAT file USERVPD.CFG Copied to the workstation as USERVPD.CFG. No USERVPD.DAT file created. USERVPD.SMP Copied to the workstation as USERVPD.SMP. No USERVPD.DAT file created. See Formatted USERVPD Data for more information on the field-defined source file for USERVPD.DAT., and Rules for Defining the USERVPD.CFG File for information on how to structure the the field-defined source file. Note that in the last two cases, USERVPD.DAT is not created automatically. If USERVPD.SMP was copied to the workstation, and you want to use USERVPD.DAT, you will need to modify USERVPD.SMP to specify the information for the station, and rename it to USERVPD.DAT. In the case of USERVPD.CFG, modify the file and then run the CVT_VPD utility to create the USERVPD.DAT file. ΓòÉΓòÉΓòÉ 6.2.2.2.1. Formatted USERVPD Data ΓòÉΓòÉΓòÉ To create user data that can be captured by QUERYVPD or QDOSVPD commands, included in the LMU/2 database in user-defined tables, and accessed by SQL queries, do the following: 1. Create or update the USERVPD.CFG file, which contains the field definitions and the user data 2. At the managing system with database, create a UDF.PRO file, which is the profile for the formatting utility (LMUUDF). The profile defines the tables for the user data in the LMU/2 database, and the SQL queries. 3. At the workstation, run the CVT_VPD utility (LMUCUST runs it automatically) to convert the field-defined data from the USERVPD.CFG file to the USERVPD.DAT file. To place the data in the data base for subsequent SQL queries, do the following: 1. Run the QUERYVPD or QDOSVPD program as usual. This places the user data from the USERVPD.DAT file into the LMU/2 database in the generic user data location. 2. At the managing system with database, run the formatting utility (LMUUDF) to a. Create or update your user data tables in the LMU/2 database b. Extract the user data from the generic user data location and place it in your user data tables in the LMU/2 database. Repeat the above steps whenever the user data changes. ΓòÉΓòÉΓòÉ 6.2.2.3. CRITFILE.DEF ΓòÉΓòÉΓòÉ Use a CRITFILE.DEF file with the QUERYVPD/QDOSVPD programs to keep track of: o The program level of programs that do not have SYSLEVEL.xxx files associated with them. This is especially useful in DOS workstations. o User changes to the workstation CONFIG.SYS file o Changes to other critical files in the workstations. To have the QUERYVPD/QDOSVPD programs report file characteristics (location, size, and time last modified) to the managing system, create a CRITFILE.DEF file that contains the names of files to check in the workstation: 1. Copy the sample LMU/2 CRITFILE.SMP file to CRITFILE.DEF. 2. Edit CRITFILE.DEF to contain a list of files for QUERYVPD or QDOSVPD to check. Use one filename per line. The filename may be fully qualified (drive\path\filename.ext) or unqualified (filename.ext only). Note: In the case of unqualified filenames, every logical drive (local and remote) for the workstation will be searched until the file is located; the search may take a long time. 3. Place the completed CRITFILE.DEF file in a directory pointed to by the workstation DPATH statement (OS/2 station only), or in the root directory of the workstation boot disk. The QUERYVPD (OS/2) search order for locating the CRITFILE.DEF file is: a. Current directory in which QUERYVPD is executing b. Directories specified in DPATH statement c. Root directory of the boot drive. The QDOSVPD (DOS) search order for locating the CRITFILE.DEF file is: a. Current directory in which QDOSVPD is executing b. Root directory of the boot drive. ΓòÉΓòÉΓòÉ 6.2.2.4. ADAPTERS.DEF ΓòÉΓòÉΓòÉ To identify Micro Channel adapters that are currently unknown to the QUERYVPD/QDOSVPD programs, in order to pass the adapter identities to the LMU/2 database as part of the QUERYVPD or QDOSVPD output, create an ADAPTERS.DEF file, as follows: 1. Copy the sample LMU/2 ADAPTERS.SMP file to ADAPTERS.DEF. 2. Edit ADAPTERS.DEF to contain a list of up to 50 adapter IDs and descriptions. Use one adapter per line, as follows: o Adapter ID -- 4 hexadecimal digits. o One space o Adapter description -- up to 70 characters. This is usually the manufacturer's description for the adapter. Examples: adapter ID adapter description Γöé Γöé ΓöîΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ | | Γöé Γöé EF00 Galaxy 60 Gigabyte Memory adapter F27D Phunnie 16/4 Fishnet adapter Adapters already known to the QUERYVPD/QDOSVPD programs are contained in ADAPTERS.TBL and can not be redefined. 3. Place the completed ADAPTERS.DEF file in a directory pointed to by the workstation DPATH statement (OS/2 station only), or in the root directory of the workstation boot disk. On a shared disk, we recommend that you put the ADAPTERS.DEF file in the same directory as the LMU/2 code; there will be only one copy of the file, and all users will have access to it. The QUERYVPD (OS/2) search order for locating the ADAPTERS.DEF file is: a. Working directory, if specified in QUERYVPD parameters b. Current directory in which QUERYVPD is executing c. Directories specified in DPATH statement d. Root directory of the boot drive. The QDOSVPD (DOS) search order for locating the ADAPTERS.DEF file is: a. Working directory, if specified in QDOSVPD parameters b. Current directory in which QDOSVPD is executing c. Root directory of the boot drive. ΓòÉΓòÉΓòÉ 6.2.2.5. APPWATCH File Table ΓòÉΓòÉΓòÉ To identify application programs to monitor in a workstation, such as critical applications, excessive instances of applications, or unwanted applications, and to generate an alert when a specified number of violations occur, create an APPWATCH file table, as follows: 1. Copy the sample LMU/2 APPWATCH.SMP file to APPWATCH.TAB or another name of your choosing. 2. Edit APPWATCH.TAB to contain a list of application programs to monitor. Use one application program per line, as follows: o Application name -- Up to 8 characters. Required. o space o Minimum instances -- The least number of occurrences of the application program that should be loaded in the workstation at all times. The range is 1 - 256. The default is 1. o space o Maximum instances -- The most occurrences of the application program that should be loaded in the workstation at one time. The range is 1 - 256. The default is 1. o space o Threshold -- The number of times the application program is found to be in violation before an alert is sent (violation = loaded in the workstation less than the minimum or more than the maximum instances specified). The range is 1 - 128. The default is 1. o space o Counter reset -- 1 character. - R (reset) -- Reset the violation count after an alert is sent. - A (accumulate) -- Do not reset the violation count after an alert is sent. The default is R (reset). An asterisk can be used as a place holder in any of the fields on a line; the default value for that field will be used. Sample APPWATCH file table: # # Sample application table # # Appl Name Minimum Maximum Threshold Reset/Accumulate # ----------- ------- ------- --------- ---------------- LMUSRV.EXE LMUCLI.EXE * * 1 A LMUIPL.SYS * 1 * * AUEPITCH.EXE 1 2 * R KLONDIKE.EXE 0 0 2 A # # Where: # Appl Name Application name: # - For OS/2 1.x this is the internal process name # of the application (1 to 8 characters); # - For OS/2 2.0 this is the file name (including # extension) of the application (1 to 12 characters) # Minimum Minimum instances of application; range is 0 to 256; # default is 1 # Maximum Maximum instances of application; range is 0 to 256; # default is 1 # Threshold Number of violations (process instances not between # minimum and maximum) before an alert is sent; # range is 1 128; default is 1 # Reset/Accumulate R[ESET] indicates that the violation count should # be reset to zero after an alert is sent; # A[CCUMULATE] indicates that the violation count # should not be reset after an alert is sent; # default is RESET # # # Notes: # - Only application name is required # - Use an asterisk (*) as a place holder (default value of entry is used) # - Table entries are order dependent but not column dependent # - Seperate table entries with one or more blanks # ΓòÉΓòÉΓòÉ 6.2.3. Running LMUCUST ΓòÉΓòÉΓòÉ To customize OS/2 stations that will be running LMU/2 programs, run LMUCUST in each station. The OS/2 station being customized must be running the IBM OS/2 LAN Requester or the Novell NetWare Requester for OS/2, or both. LMUCUST creates or updates necessary files on the station. After running LMUCUST, be sure to review all of Preparing the Environment (from topic Preparing the Environment to Handling Generic Alerts) to make certain you have performed all necessary tasks in each station. The LMUCUST syntax follows. ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUCUST ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /spath ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ- /Tx ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ MANAGING ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöñ Γöé Γö£ΓöÇΓöÇ NO_DATABASE ΓöÇΓöñ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇ ALERTS ΓöÇΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇΓöÇΓö¼ΓöÇ ADMINISTRATOR ΓöÇΓö¼ΓöÇΓöñ Γöé ΓööΓöÇ NO_GROUP_FOLD ΓöÇΓöÿ Γöé Γö£ΓöÇΓöÇΓö¼ΓöÇ FAULT_MANAGER ΓöÇΓö¼ΓöÇΓöñ Γöé Γö£ΓöÇΓöÇΓöÇΓöÇ NETVIEW ΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γö£ΓöÇΓöÇ LAN_MANAGER ΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇΓöÇ NO_FORWARD ΓöÇΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇΓöÇΓöÇΓöÇ FAULT_REPORTER ΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ MANAGED ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ NO_EDIT ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Display Help information. /spath spath is the subdirectory inserted in the LIBPATH and PATH statements in your CONFIG.SYS where LMU/2 programs are to be found. SPATH defaults to the subdirectory from which LMUCUST.EXE is being executed. /Tx The target drive for workstation specific files and backup files. If customizing from a shared drive the default is the OS/2 boot drive. MANAGING Workstation being configured will listen for heartbeats from the managed systems, and will maintain the LMU/2 database (unless NO_DATABASE parameter specified). NO_DATABASE Managing workstation being configured will not maintain the LMU/2 database. ALERTS Managing workstation's alert generation is enabled. ADMINISTRATOR Workstation being configured will have ability to issue controlling commands to the managed systems. NO_GROUP_FOLD No Group/Folder will be built for the ADMINISTRATOR workstation. FAULT_MANAGER Workstation being configured will handle generic alerts originating from a workstation. NETVIEW Fault Manager will forward alerts to NETVIEW. LAN MANAGER Fault Manager will forward alerts to the LAN management functional address. NO_FORWARD Fault Manager will not forward alerts. FAULT_REPORTER Workstation being configured will route generic alerts from OS/2 subsystems and applications in a workstation to the Fault Manager. MANAGED Workstation being configured will receive controlling commands, execute the requested programs, and send requested information to the managing system. NO_EDIT STARTUP.CMD and CONFIG.SYS will not be modified. LMUCUST Help Information Important If spath is not specified, LMUCUST must be executed from the directory in which the LMU/2 software was installed. If spath is specified, LMUCUST may be executed from the LAN Management Utilities/2 diskette, but spath cannot specify the A: drive. Run LMUCUST in each LMU/2 OS/2 station, specifying the functions the station is to perform. Enter any combination of functions, in any order. Parameters: o The ? option produces the help panel. o The /spath option specifies the drive and path of the LMU/2 software. LMUCUST adds this drive and path to the PATH and LIBPATH statements in the station CONFIG.SYS file. If this option is omitted, LMUCUST uses the drive and path of the directory from which it is executing. Note: Spath cannot point to the A: drive. o The Tx option specifies the drive to which workstation-specific files (such as computername.CTL) and backup files (such as STARTUP.BAK) will be copied during customization. The subdirectory is always LMU2. For example: LMUCUST MANAGED /Td will copy needed files to D:\LMU2. If Tx is not specified, the default drive is the OS/2 boot drive. o The MANAGING option indicates that the station is to serve as a managing system. The station will maintain an LMU/2 database (will serve as a managing system with database), unless NO_DATABASE is also specified, and will listen for heartbeats from managed systems. This option includes fault reporting. STARTUP.CMD will be modified. o The NO_DATABASE option indicates that the managing system being configured is not to maintain the LMU/2 database (the LMUSRV command will be set up with the /r parameter). This option is valid only when the MANAGING option is specified. Note: Make sure that at least one managing system on the network maintains an LMU/2 database. o The ALERTS option indicates that LMUSRV in the managing system being configured is to generate alerts. That is, the LMUSRV command will be set up with the /a parameter, enabling all alerts. This option is valid only when the MANAGING option is specified. o The ADMINISTRATOR option indicates that the station is to serve as an administrator workstation. This option does not cause a modification to STARTUP.CMD. o The NO_GROUP_FOLD option indicates that LMUCUST is not to set up a group or a desktop folder. The group or folder contains selections to: - View the LMU/2 documentation - Start the LMU/2 graphical user interface - Start the LMU/2 schedule editor - Start the LMU/2 group editor - Start the LMU/2 scheduler - Terminate the LMU/2 programs - Shut down the workstation The default in an OS/2 1.3 workstation is to set up the group; the default in an OS/2 2.0 workstation is to set up the desktop folder. o The FAULT_MANAGER option indicates that the station is to serve as a fault manager. STARTUP.CMD will be modified. Note: If the fault manager component is serving as the IBM LAN Network Manager (LNM) alerts user exit, do not use the FAULT_MANAGER option on the LNM station. Instead, designate another station as the LMU/2 alerts focal point (see Customizing the Fault Manager for details) and use the FAULT_MANAGER option on the focal point station. o The NETVIEW option indicates that the fault manager is to forward alerts to IBM NetView. The AUECATCH command is set up with a parameter of 1. This option is valid only when the FAULT_MANAGER option is specified. o The LAN_MANAGER option indicates that the fault manager is to forward alerts to a LAN management functional address, such as the IBM LAN Network Manager. The AUECATCH command is set up with a parameter of 2. o The NO_FORWARD option indicates that the fault manager is not to forward alerts. The AUECATCH command is set up with a parameter of 3. o The FAULT_REPORTER option indicates that the station is to serve as a fault reporter. It is not necessary to specify FAULT_REPORTER if MANAGING or MANAGED are also specified. STARTUP.CMD will be modified. o The MANAGED option indicates that the station is to serve as a managed system. This option includes fault reporting. STARTUP.CMD will be modified. o The NO_EDIT option specifies that the workstation's STARTUP.CMD and CONFIG.SYS files are not to be modified by the LMUCUST program. The user will need to make the necessary updates manually. This option does not affect the building of the LMUSTART.CMD file. Example: If the station is to serve as a managed, managing, and fault manager system, with fault reporting, you can use the following command: LMUCUST MANAGING MANAGED FAULT_MANAGER or: LMUCUST /drive:\path MANAGING MANAGED FAULT_MANAGER LMUCUST looks in the directory from which it is executing for the files it needs for customizing. If LMUCUST finds the necessary input files (described in topics All OS/2 Stations through Creating USERVPD.DAT), it creates the LMU.INI file and USERVPD.DAT files. Otherwise, you must customize the sample files and generate LMU.INI and (optionally) USERVPD.DAT yourself. LMUCUST searches for the user-defined control files (computername.CTL, domain.CTL, LMU.CTL, for example) according to the table below: +-------------------------------------------------------------------+ ! Customizing ! ! From /Tx ! ! Shared Parameter Searches Other ! ! Drive Specified First Search ! !------------------------------------------------------------------ ! ! ! ! NO Specified x:\LMU2 Wherever LMUCUST resides ! !------------------------------------------------------------------ ! ! YES Specified x:\LMU2 Wherever LMUCUST resides ! !------------------------------------------------------------------ ! ! NO Not specified ---- Wherever LMUCUST resides ! ! (only) ! !------------------------------------------------------------------ ! ! YES Not specified y:\LMU2* Wherever LMUCUST resides ! +-------------------------------------------------------------------+ * y represents the boot drive For example, if LMUCUST is customizing from a shared drive (resides on and executes from a shared drive), and the /Tx parameter is specified, LMUCUST first searches the LMU2 directory on the drive specified by the /T parameter; if the control files are not found there, LMUCUST then searches its own directory. If LMUCUST is customizing from a shared drive and the /Tx parameter is not specified, it first searches the LMU2 directory on the boot drive for the control files; if the control files are not found there, LMUCUST then searches its own directory. LMUCUST copies any other necessary files, then modifies the CONFIG.SYS file. Depending on the functions specified on the LMUCUST command line, LMUCUST creates an LMUSTART.CMD file in the C:\LMU2 directory and modifies the STARTUP.CMD file to call LMUSTART.CMD. If no functions are specified, LMUCUST does not modify STARTUP.CMD. See topic STARTUP.CMD Statements for the statements placed in LMUSTART.CMD. Note: For managing stations that are not to maintain an LMU/2 database, make sure that the START LMUSRV.EXE command in the LMUSTART.CMD file uses the /r option (START LMUSRV.EXE /r). Make sure that at least one managing station in the network maintains an LMU/2 database. If LMUCUST attempts to modify the STARTUP.CMD file and is unable to do so, you must create or modify the STARTUP.CMD file to include a call to the LMUSTART.CMD file. Place the call somewhere after the statements that start the LAN server or requester and that access the disk that contains the LMU/2 software. Make certain the LAN server or requester is running before issuing the call to LMUSTART.CMD. This is the call statement to use: CALL d:\LMU2\LMUSTART.CMD where d is the drive containing the LMU/2 software. If the contents of the STARTUP.CMD file are written in REXX, enclose the call statement in single quotes: 'CALL d:\LMU2\LMUSTART.CMD' Restart the computer after running LMUCUST, to activate the CONFIG.SYS and STARTUP.CMD changes. Note: If the station is a fault manager, see the section Special Considerations for Fault Managers before restarting the computer. ΓòÉΓòÉΓòÉ 6.2.3.1. Special Considerations for Fault Managers ΓòÉΓòÉΓòÉ If a station is a fault manager, create the alerts table described in User-Defined Table before restarting the computer. If the fault manager is to function as the alerts user exit routine for the IBM LAN Network Manager (LNM), you must remove any START AUECATCH command from the LMUSTART.CMD file of the LNM station. The fault manager main module, AUEDRIVR.DLL, is specified in LNM as the user alert filter and runs in the LNM station, but AUECATCH does not function with LNM. To enable the fault manager to receive LMU/2 alerts when serving as the LNM user exit routine, start AUECATCH in another station as follows: 1. Specify the LNM adapter address as the FM_FORWARDING_ADDR in the LMU.INI file of the non-LNM station. 2. Start AUECATCH in the non-LNM station, with the option to forward alerts to a LAN management address (AUECATCH 2). 3. In the LMU.INI file in stations running the fault reporter component, identify the station running AUECATCH as the fault manager station (FAULT_MANAGER). Do not identify the LNM station as the fault manager. After the computers are restarted, LMU/2 alerts are directed to the station running AUECATCH, which can then forward the alerts to the LNM through the Alert Transport Service. Note: If the LNM has the only LAN management functional address in the network, or the only controlling LNM, it is not necessary to specify an FM_FORWARDING_ADDR in the AUECATCH station LMU.INI file. ΓòÉΓòÉΓòÉ 6.3. Installation for a DOS Station ΓòÉΓòÉΓòÉ Note: This topic applies to a workstation running an IBM DOS LAN Requester, or Novell NetWare Requester for DOS, or both. If the DOS station has access to a shared disk that contains the LMU/2 software, no programs need to be copied to the DOS station. Customize the station as described in Customizing a DOS Station. If the DOS station does not have access to a shared disk that contains the LMU/2 software, copy the following modules from the LAN Management Utilities/2 diskette 3 to the DOS computer: o DOSVIRGA.COM o QDOSVPD.COM o LMUDOSHB.COM o USERVPD.SMP (optional) if you want to supply specific identifying information about the computer in QDOSVPD configuration data. o AUEDOSAL.COM o ADAPTERS.SMP (optional) if you want to identify adapters not known to the QDOSVPD program o CRITFILE.SMP (optional) if you want the QDOSVPD program to report on selected files for you o ADAPTERS.TBL o CVT_VPD.EXE ΓòÉΓòÉΓòÉ 6.4. Customizing a DOS Station ΓòÉΓòÉΓòÉ Note: This topic applies to a workstation running an IBM DOS LAN Requester, or Novell NetWare Requester for DOS, or both. To provide specific machine identification with the configuration data produced by the QDOSVPD command, create a USERVPD.DAT file using one of the following methods: o Copy USERVPD.SMP to the C: root directory in the DOS computer or to a directory that will be specified by the /w option on the QDOSVPD command, rename the copy to USERVPD.DAT, and modify the contents to contain up to 3500 bytes of user data. The USERVPD.SMP file contains all instructions necessary. o Create a USERVPD.CFG file as described in Formatted USERVPD Data, to create a USERVPD.DAT file that contains fields that can be included in the LMU/2 database. To provide identification of adapters that are currently unknown to the QDOSVPD program, create an ADAPTERS.DEF file as described in the topic ADAPTERS.DEF. To track changes to critical programs and other files in the workstation, create a CRITFILE.DEF file as described in the topic CRITFILE.DEF. The LMU/2 commands require NETBIOS support; you may need to modify the CONFIG.SYS file in the DOS workstation to provide additional NETBIOS resources needed by the LMU/2 commands. See the topic CONFIG.SYS Statements for details. Optionally, modify the following files: o CONFIG.SYS, to specify the location of the LMU/2 software in the search path. Otherwise, you may need to specify the drive and subdirectory on the command to execute a program. o AUTOEXEC.BAT, to add the following statements: SET FAULT_MANAGER=computer name and LMUDOSHB managing-system where computer name specifies the fault manager computer, and managing-system specifies the managing system for the DOS station. If the fault manager computer is an IBM LAN Requester, computer name is the COMPUTERNAME specified in the fault manager IBMLAN.INI file; if the fault manager computer is a Novell NetWare Requester for DOS, computer name is the Novell internetwork address of the fault manager computer. The same applies to managing-system. If desired, you can also add the QDOSVPD statement, causing QDOSVPD to execute upon station startup. ΓòÉΓòÉΓòÉ 6.5. Installation for a Novell NetWare Server ΓòÉΓòÉΓòÉ A Novell NetWare Server can be an LMU/2 managed system, it can simply maintain the shared drive that contains the LMU/2 programs and files needed by NetWare Requesters, or it can do both. NetWare file server: To install the LMU/2 programs and files on a Novell NetWare Server that maintains the shared drive of LMU/2 software and files (regardless of whether the NetWare Server will be a managed system), run the LMUINST program on a station that is running the Novell NetWare Requester for OS/2, and specify a drive on the NetWare Server as the target drive. Example: LMUINST NETWARE /tg places all LMU/2 support for NetWare Requesters and Servers onto the server drive that is mapped to G: by the workstation in which LMUINST is executing. If the server is to be an LMU/2 managed system, it must be customized and then rebooted; see Customizing a Novell NetWare Server. NetWare Server as managed system only: If you do not plan to provide the OS/2 or DOS LMU/2 support to NetWare Requesters from a particular NetWare Server that will be an LMU/2 managed system, it is not necessary to run LMUINST for that server. At a Novell NetWare Requester station, copy the following modules from the LMU/2 Diskette 3 to the server station's NetWare partition: o LMUBIND.SMP o All .NLM modules (*.NLM) o ADAPTERS.SMP o CRITFILE.SMP o USERVPD.SMP o ADAPTERS.TBL and copy the following modules to the server station's DOS partition: o QDOSVPD.COM o LMUDOSHB.COM o CVT_VPD.EXE After copying the modules, you need to customize the server, then restart the system; see Customizing a Novell NetWare Server. ΓòÉΓòÉΓòÉ 6.6. Customizing a Novell NetWare Server ΓòÉΓòÉΓòÉ To enable a Novell NetWare Server to be a managed station, you must define certain values needed by the LMU/2 functions, and you must execute the LMU/2 customization programs for a NetWare Server. 1. Make sure DOS is present in the NetWare Server machine. 2. Copy the LMUBIND.SMP file to LMUBIND.CTL in the volume and path you will use for the LMU/2 programs. In LMUBIND.CTL, set the values for the managing system, managing system with database, fault manager, message log, and heartbeat pulse rate for the NetWare Server. This information will be placed in the bindery in the NetWare Server by the conversion programs. The properties are explained in the topic Sample LMUBIND.CTL File. 3. Run the following programs, in the following order: a. LMUBNDCS.NLM - Loads the bindery with the LMU/2 control variables from the LMUBIND.CTL file. b. LMUNLMCS.NLM - Modifies the AUTOEXEC.BAT file and the bindery. Places the location of the AUTOEXEC.BAT file in the bindery. c. LMUNCFCS.NLM - Modifies the AUTOEXEC.NCF file to add: o SEARCH ADD command for the volume and path of the LMU/2 programs. o LOAD of QUERYVPD.NLM o LOAD of LMUCLI.NLM d. LMUVPDCS.NLM - Copies QDOSVPD.COM and the ADAPTERS.TBL file to the DOS partition, into the same path as the AUTOEXEC.BAT file. e. LMUTBLCS.NLM - Optional. Execute this program only if you have created an ADAPTERS.DEF file. LMUTBLCS.NLM Copies the ADAPTERS.DEF file to the DOS partition, into the same path as the AUTOEXEC.BAT file. 4. Restart the computer. You need to do this only once. After customization is complete, you can use the LMULOAD program at any time to view and modify the LMU/2 property values in the bindary. ΓòÉΓòÉΓòÉ 6.6.1. Sample LMUBIND.CTL File ΓòÉΓòÉΓòÉ A sample LMUBIND.CTL file is provided with LMU/2 as LMUBIND.SMP. Copy LMUBIND.SMP to LMUBIND.CTL in the NetWare partition where the LMU/2 programs reside, and modify the property values to fit your Novell NetWare Server. Do not change the names of the properties. The properties are described below. The names in parentheses are the terms used in the LMULOAD program. MANAGING_SYSTEM (Managing System) The internetwork address of the OS/2 machine that is to monitor the heartbeat status of this NetWare Server. M_WITH_DATABASE (Database Machine) The internetwork address of the OS/2 machine that is the managing system with database, or database machine. This is the station that will receive data from the LMU/2 management applications in the NetWare Server for inclusion in the LMU/2 database. The station named must be running the managing system software (LMUSRV), must maintain an LMU/2 database, and can be the same station as MANAGING SYSTEM. FAULT_MANAGER (Fault Manager) The internetwork address of the OS/2 machine to which the LMU/2 management applications in the NetWare Server are to route generic alerts for handling. The station named must be running the LMU/2 fault manager software and must have a user-defined table of alerts in the station. MESSAGE_LOG (LMU/2 Message Log) The volume, path, and file name of the LMU/2 message log on this NetWare Server. PULSE_RATE (Pulse Rate) The interval, in minutes, for heartbeat messages from LMUCLI in the NetWare Server to the managing system. A value of 0000 specifies that only the initialization and termination messages will be sent. The value is in hexadecimal, four digits. Additional properties are defined by the customization programs during the customization process. After customization is complete, you can view all the LMU/2 properties using the LMULOAD program. ΓòÉΓòÉΓòÉ 6.7. Preparing the Environment ΓòÉΓòÉΓòÉ After the LMU/2 software has been installed on each station or on a shared disk, the next step is to create or update required files on each station. After you run LMUCUST, review the topics in this section to be sure that your environment is properly prepared. Topics in this Section: NETBIOS LMU.INI File Specifying LMU.INI Variables Creating the LMU.INI File Sample LMU/2 Control File LMU/2 Control File Variables CONFIG.SYS Statements STARTUP.CMD Statements Copying Required Files Other Software Installation Creating the Database Handling Generic Alerts ΓòÉΓòÉΓòÉ 6.7.1. NETBIOS ΓòÉΓòÉΓòÉ In an IBM OS/2 LAN Requester environment: Various components of LMU/2 use NETBIOS for machine to machine communication. You may need to increase your NETBIOS resources at each IBM OS/2 LAN Requester workstation. The additional NETBIOS resources that may be required at each affected station are: RESOURCE AMOUNT NETBIOS Commands 20 NETBIOS Names 20 NETBIOS Sessions 20 In an IBM DOS LAN Requester environment: The LMU/2 programs for DOS managed systems require NETBIOS support; you may need to modify the CONFIG.SYS file in the DOS workstation to provide additional NETBIOS resources needed by the LMU/2 commands. See the topic CONFIG.SYS Statements for details. In a Novell NetWare Requester environment: NETBIOS support is not required. ΓòÉΓòÉΓòÉ 6.7.2. LMU.INI File ΓòÉΓòÉΓòÉ The IBM LAN Management Utilities/2 uses a set of program variables that are contained in a .INI file called LMU.INI. Each LMU/2 OS/2 station contains its own LMU.INI file, with values that are relative to that station. LMU.INI must reside in the root directory of the C: drive of the workstation. Note: DOS stations do not use an LMU.INI file. The LMU.INI variables include such items as: o The identity of the managing station o The identity of the LMU/2 database station o The identity of the fault manager station o The location of the fault management user-written alerts table o The location of the LMU/2 database BIND statements o The location of the LMU/2 message log o The location of the LMU/2 change log o The LMU/2 pulse rate ("heartbeat" rate) o The threshold specifications for the performance commands. and others. ΓòÉΓòÉΓòÉ 6.7.2.1. Specifying LMU.INI Variables ΓòÉΓòÉΓòÉ LMU.INI is built from a text data control file that contains the values to use for the variables. A sample control file, LMUCTL.SMP, is supplied on the LAN Management Utilities/2 diskette. The statements used in a control file are explained in Control File for DPRG, DINI, LINI. The variables used in the LMU/2 control file are explained in LMU/2 Control File Variables. ΓòÉΓòÉΓòÉ 6.7.2.2. Creating the LMU.INI File ΓòÉΓòÉΓòÉ LMU.INI is built at each OS/2 workstation as part of the LMU/2 installation and configuration process. To build the LMU.INI file in a workstation: 1. Copy LMUCTL.SMP to create an LMU/2 control file in the workstation 2. Customize the LMU/2 control file with the values for the workstation. 3. Run the LINI.EXE program in the workstation, specifying the LMU/2 control file as input. To change the LMU.INI file in a workstation: 1. Change the contents of the LMU/2 control file 2. Run the LINI.EXE program in the workstation, specifying the LMU/2 control file as input. In either case, the LINI program places the resulting LMU.INI file in the root directory of the workstation C: drive. Note: For IBM OS/2 LAN Requester stations, the customization program, LMUCUST, automatically builds the initial LMU.INI file from your control file if you name the control file and place it as specified in the topic About Creating LMU.INI. Important Once the LMU.INI file has been built, changes made in the LMU/2 control file are implemented in LMU.INI only if you run the LINI program again and specify the revised LMU/2 control file as input. ΓòÉΓòÉΓòÉ 6.7.2.3. Sample LMU/2 Control File ΓòÉΓòÉΓòÉ Below is a sample LMU/2 control file. Note the use of the pound sign for comment lines. The punctuation (commas and semicolons) and indentations are included for readability. The LINI program ignores them. This sample identifies all the keywords. The values shown in this sample must be replaced with information specific to your network and workstation. Do not change anything on the DEFINE_PROFILE INI_FILE(C:\LMU.INI) line. Do not change the application value (uppercase LMU_UTILITY) or the key names (uppercase MESSAGE_LOG, MANAGING_SYSTEM, PULSE_RATE, and so forth). ################################################################# # IDENTIFIES THE PATH AND FILENAME OF THE LMU PROFILE. # # LMU.INI MUST RESIDE ON THE OS/2 BOOT DRIVE. THE NAME OF # # THE PROFILE MUST REMAIN LMU.INI. # ################################################################# DEFINE_PROFILE INI_FILE(C:\LMU.INI) ################################################################# # THE FOLLOWING PARAMETERS APPLY TO ALL SYSTEMS. # ################################################################# # Identifies the location of the file to contain # the messages issued by LMU. APP(LMU_UTILITY), KEY(MESSAGE_LOG), ASCIIZ(path\filename); ################################################################# # THE FOLLOWING PARAMETERS APPLY TO "MANAGED" SYSTEMS. # ################################################################# # Identifies this workstation's managing system. APP(LMU_UTILITY), KEY(MANAGING_SYSTEM), ASCIIZ(computername or internetwork address); # Identifies this workstation's managing system with database, # which is the system maintaining the LMU database. APP(LMU_UTILITY), KEY(MANAGING_SYSTEM_WITH_DATABASE), ASCIIZ(computername or internetwork address); # Identifies this workstation's fault manager, which is # the system to receive all generic alerts generated by this workstation. APP(LMU_UTILITY), KEY(FAULT_MANAGER), ASCIIZ(computername or internetwork address); # Identifies the frequency in minutes that the heartbeat # function will send a message to the managing system. # # NOTE: The hexnum value for PULSE_RATE must be specified # as 4 hexadecimal digits, e.g. (000A) to indicate 10 minutes. APP(LMU_UTILITY), KEY(PULSE_RATE), HNUM(hexnum-4); ################################################################# # THE FOLLOWING PARAMETERS APPLY TO THE PERFWACH UTILITY. # ################################################################# # Identifies the default percentage threshold for process execution - # For additional information see PERFWACH documentation. APP(LMU_UTILITY), KEY(PERFWACH_PROC) ASCIIZ(decnum); # Identifies the default percentage threshold for disk activity - # For additional information see PERFWACH documentation. APP(LMU_UTILITY), KEY(PERFWACH_DISK) ASCIIZ(decnum); # Identifies the default percentage threshold for swap activity - # For additional information see PERFWACH documentation. APP(LMU_UTILITY), KEY(PERFWACH_SWAP) ASCIIZ(decnum); # Identifies the default percentage threshold for free memory - # For additional information see PERFWACH documentation. APP(LMU_UTILITY), KEY(PERFWACH_FREE) ASCIIZ(decnum); # Identifies the default percentage threshold for total CPU utilization - # For additional information see PERFWACH documentation. APP(LMU_UTILITY), KEY(PERFWACH_TCPU) ASCIIZ(decnum); ################################################################# # THE FOLLOWING PARAMETERS APPLY TO THE OSRWATCH UTILITY. # ################################################################# # Identifies the default percentage threshold for # the number of available NCBS - # For additional information see OSRWATCH documentation. APP(LMU_UTILITY), KEY(OSRWATCH_NCBS) ASCIIZ(decnum); # Identifies the default percentage threshold for # the number of available sessions - # For additional information see OSRWATCH documentation. APP(LMU_UTILITY), KEY(OSRWATCH_NSES) ASCIIZ(decnum); # Identifies the default threshold for # the number of packet errors - # For additional information see OSRWATCH documentation. APP(LMU_UTILITY), KEY(OSRWATCH_NERR) ASCIIZ(decnum); # Identifies the default threshold for # the number of aborted transmissions - # For additional information see OSRWATCH documentation. APP(LMU_UTILITY), KEY(OSRWATCH_NABT) ASCIIZ(decnum); # Identifies the default threshold for # the number of DLC time outs (both inactivity Ti and response T1). # For additional information see OSRWATCH documentation. APP(LMU_UTILITY), KEY(OSRWATCH_NDTO) ASCIIZ(decnum); # Identifies the default threshold for # the number of adapter buffers exausted - # For additional information see OSRWATCH documentation. APP(LMU_UTILITY), KEY(OSRWATCH_NBFX) ASCIIZ(decnum); # Identifies the default threshold for # the number of users logged on - # For additional information see OSRWATCH documentation. APP(LMU_UTILITY), KEY(OSRWATCH_NLGN) ASCIIZ(decnum); # Identifies the default percentage threshold for # the number of DLC inactivity time outs (Ti only). # For additional information see OSRWATCH documentation. APP(LMU_UTILITY), KEY(OSRWATCH_NDTI) ASCIIZ(decnum); # Identifies the default percentage threshold for # the number of DLC response time outs (T1 only). # For additional information see OSRWATCH documentation. APP(LMU_UTILITY), KEY(OSRWATCH_NDT1) ASCIIZ(decnum); ################################################################# # THE FOLLOWING OPTIONAL PARAMETER APPLIES TO THE OSRWATCH # # UTILITY AND TO "ADMINISTRATOR" AND "FAULT MANAGER" SYSTEMS. # ################################################################# # Identifies the default adapter used in direct NETBIOS # functions (LMUCMD and OSRWATCH). Value 00 indicates the # primary adapter and value 01 indicates the secondary adapter. # This key is optional and if not specified LMUCMD and OSRWATCH # will use the primary adapter. # # NOTE: The hexnum value for LAN_ADAPTER must be specified # as 2 hexadecimal digits (for example, 01). APP(LMU_UTILITY), KEY(LAN_ADAPTER), HNUM(hexnum-2); ################################################################# # THE FOLLOWING PARAMETERS APPLY TO THE SRVWATCH UTILITY. # ################################################################# # Identifies the default threshold for # server average response time - # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_SAVR) ASCIIZ(decnumthreshold,decnumcount); # Identifies the default threshold for # server request buffer allocation failures - # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_SRBF) ASCIIZ(decnum); # Identifies the default threshold for # big buffer allocation failures - # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_SBBF) ASCIIZ(decnum); # Identifies the default threshold for # total session count at the server. # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_TSES) ASCIIZ(decnum); # Identifies the default threshold for # total connection count at the server. # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_TCON) ASCIIZ(decnum); # Identifies the default threshold for # total open file count at the server. # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_TOPN) ASCIIZ(decnum); # Identifies the default threshold for # the number of sessions in use by a single user. # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_SSES) ASCIIZ(decnum); # Identifies the default threshold for # the number of connections in use by a single user. # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_SCON) ASCIIZ(decnum); # Identifies the default threshold for # the number of file opens by a single user. # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_SOPN) ASCIIZ(decnum); # Identifies the default threshold for # the time a user session is idle (in minutes). # For additional information see SRVWATCH documentation. APP(LMU_UTILITY), KEY(SRVWATCH_SIDL) ASCIIZ(decnum); ################################################################# # THE FOLLOWING PARAMETERS APPLY TO "MANAGING" SYSTEMS. # ################################################################# # Identifies the location in which the # LMUSRV*.BND files were installed. APP(LMU_UTILITY), KEY(BIND), ASCIIZ(path); # Identifies the file to contain # the node description change log. APP(LMU_UTILITY), KEY(CHANGE_LOG), ASCIIZ(path\filename); # Identifies the location to which transfered # files are to written. APP(LMU_UTILITY), KEY(FILE_PATH), ASCIIZ(path); ################################################################# # THE FOLLOWING PARAMETERS APPLY TO "FAULT MANAGER" SYSTEMS. # ################################################################# # Identifies the Fault Manager's input user table. # For example AUEUSER.SMP APP(LMU_UTILITY), KEY(FAULT_TABLE), ASCIIZ(path\filename); # Alerts can be forwarded to a specific adapter address if desired. # This key is optional and if not specified the default LAN management # functional address of 'C00000002000' is used. APP(LMU_UTILITY), KEY(FM_FORWARDING_ADDR), ASCIIZ(adapter_num); ################################################################# # THE FOLLOWING PARAMETERS APPLY TO THE LMU/2 SCHEDULER. # ################################################################# # Identifies the path and file name of the Schedule log file # For example C:\LMU2\SCHEDULE.LOG APP(LMU_UTILITY), KEY(SCHEDULE_LOG), ASCIIZ(path\filename); # Identifies the path and file name of the Schedule file # For example C:\LMU2\SCHEDULE.TIM APP(LMU_UTILITY), KEY(SCHEDULE_FILE), ASCIIZ(path\filename); # Identifies the path and file name of the Schedule group file # For example C:\LMU2\SCHEDULE.GRP APP(LMU_UTILITY), KEY(SCHEDULE_GROUP_FILE), ASCIIZ(path\filename); # Identifies the frequency in minutes that the schedule # file will be checked for changes. # For example 60 APP(LMU_UTILITY), KEY(SCHEDULE_READ), ASCIIZ(num_minutes); ΓòÉΓòÉΓòÉ 6.7.2.4. LMU/2 Control File Variables ΓòÉΓòÉΓòÉ The LAN Management Utilities/2 variables for a workstation are defined using the keywords described below. The sample LMU/2 control file (LMUCTL.SMP) shipped on the LMU/2 diskette includes all the keywords. MESSAGE_LOG Specifies the path and name of the file to which LMU/2 programs in this workstation are to write messages. To facilitate problem determination, this file should be unique to this workstation (that is, the message log should not be a common file written to by multiple stations). MANAGING_SYSTEM Identifies the station that is the managing system to this workstation. If this workstation is a managed system, the managing system is the station to which LMUCLI will send heartbeats. For IBM OS/2 LAN Requester stations, the value must be the requester ID (identified by COMPUTERNAME in the IBMLAN.INI file in that station) of the managing system. If the managing system is in this workstation, the value is the requester ID of this workstation. For Novell NetWare requesters, the value is the internetwork address of the managing system. If the managing system is in this workstation, the value is the internetwork address of this workstation. MANAGING_SYSTEM_WITH_DATABASE Identifies the station to which data from this workstation will be sent for inclusion in an LMU/2 database. The station named must be running the managing system software (LMUSRV), must maintain an LMU/2 database, and may be the same station as MANAGING_SYSTEM. For IBM OS/2 LAN Requester stations, the value must be the requester ID (identified by COMPUTERNAME in the IBMLAN.INI file in that station) of the managing system with database (database machine). If the managing system with database is in this workstation, the value is the requester ID of this workstation. For Novell NetWare requesters, the value is the internetwork address of the managing system with database. If the managing system with database is in this workstation, the value is the internetwork address of this workstation. FAULT_MANAGER Identifies the station to which the fault reporter in this workstation will route generic alerts for handling. The generic alerts that will be routed are produced in this workstation by any of the following: o LMU/2 managing system o LMU/2 managed system o User-written programs that conform to the API described in Alert Generation and Routing. The station named must be running the LMU/2 fault manager software and must have a user-defined table of alerts in the station. Note: If the fault manager is serving as the IBM LAN Network Manager alerts user exit routine and you want the fault manager to handle LMU/2 alerts, the station named must be the station running AUECATCH, not the station running the LAN Network Manager. See Special Considerations for Fault Manager for details. For IBM OS/2 LAN Requester stations, the value must be the requester ID (identified by COMPUTERNAME in the IBMLAN.INI file in that station) of the fault manager station. If the fault manager is in this workstation, the value is the requester ID of this workstation. For Novell NetWare requesters, the value is the internetwork address of the fault manager station. If the fault manager is in this workstation, the value is the internetwork address of this workstation. PULSE_RATE The interval, in minutes, for heartbeat messages from LMUCLI in this workstation. A value of 0000 specifies that only the initialization and termination heartbeat messages are to be sent. Note that the value must be entered as hexadecimal, and must be four digits. If the keyword PULSE_RATE is not specified, the default value is 0000. If this workstation is not a managed system (does not run LMUCLI), the PULSE_RATE keyword does not apply. PERFWACH_PROC The PERFWACH default threshold for process activity. If this threshold is exceeded, PERFWACH generates a generic alert. This value is a percentage, and may be overridden temporarily by the /@PROCp parameter on the PERFWACH command. See the PERFWACH documentation in topic PERFWACH for more information. A value of 0 indicates "do not monitor process activity". If the keyword PERFWACH_PROC is not specified, the default value is 0. If PERFWACH is not to be run in this station, this keyword does not apply. PERFWACH_DISK The PERFWACH default threshold for disk activity. If this threshold is exceeded, PERFWACH generates a generic alert. This value is a percentage, and may be overridden temporarily by the /@DISKp parameter on the PERFWACH command. See the PERFWACH documentation in topic PERFWACH for more information. A value of 0 indicates "do not monitor disk activity". If the keyword PERFWACH_DISK is not specified, the default value is 0. If PERFWACH is not to be run in this station, this keyword does not apply. PERFWACH_SWAP The PERFWACH default threshold for swap activity. If this threshold is exceeded, PERFWACH generates a generic alert. This value is a percentage, and may be overridden temporarily by the /@SWAPp parameter on the PERFWACH command. See the PERFWACH documentation in topic PERFWACH for more information. A value of 0 indicates "do not monitor swap activity". If the keyword PERFWACH_SWAP is not specified, the default value is 0. If PERFWACH is not to be run in this station, this keyword does not apply. PERFWACH_FREE The PERFWACH default threshold for free memory availability. If the percentage of free memory in this workstation falls below this value, PERFWACH generates a generic alert. This value is a percentage, and may be overridden temporarily by the /@FREEp parameter on the PERFWACH command. See the PERFWACH documentation in topic PERFWACH for more information. A value of 0 indicates "do not monitor free memory availability". If the keyword PERFWACH_FREE is not specified, the default value is 0. If PERFWACH is not to be run in this station, this keyword does not apply. PERFWACH_TCPU The PERFWACH default threshold for total central processing unit (CPU) utilitization. If the CPU utilization exceeds this value, PERFWACH generates a generic alert. This value is a percentage, and may be overridden temporarily by the /@TCPUp parameter on the PERFWACH command. See the PERFWACH documentation in topic PERFWACH for more information. A value of 0 indicates "do not monitor CPU utilization". If the keyword PERFWACH_TCPU is not specified, the default value is 0. If PERFWACH is not to be run in this station, this keyword does not apply. OSRWATCH_NCBS The OSRWATCH default threshold for the number of available NETBIOS control blocks. This value is a percentage. If the percentage of available NETBIOS control blocks is less than this threshold, OSRWATCH generates a generic alert. This value may be overridden temporarily by the /@NCBSp parameter on the OSRWATCH command. See the OSRWATCH documentation in topic OSRWATCH for more information. A value of 0 indicates "do not monitor the number of control blocks". If the keyword OSRWATCH_NCBS is not specified, the default value is 0. If OSRWATCH is not to be run in this station, this keyword does not apply. OSRWATCH_NSES The OSRWATCH default threshold for the number of available NETBIOS sessions. This value is a percentage. If the percentage of available sessions is less than this threshold, OSRWATCH generates a generic alert. This value may be overridden temporarily by the /@NSESn parameter on the OSRWATCH command. See the OSRWATCH documentation in topic OSRWATCH for more information. A value of 0 indicates "do not monitor the number of sessions". If the keyword OSRWATCH_NSES is not specified, the default value is 0. If OSRWATCH is not to be run in this station, this keyword does not apply. OSRWATCH_NERR The OSRWATCH default threshold for the number of packet transmission errors. If this threshold is exceeded, OSRWATCH generates a generic alert. This value may be overridden temporarily by the /@NERRn parameter on the OSRWATCH command. See the OSRWATCH documentation in topic OSRWATCH for more information. A value of 0 indicates "do not monitor the number of packet errors". If the keyword OSRWATCH_NERR is not specified, the default value is 0. If OSRWATCH is not to be run in this station, this keyword does not apply. OSRWATCH_NABT The OSRWATCH default threshold for the number of aborted transmissions. If this threshold is exceeded, OSRWATCH generates a generic alert. This value may be overridden temporarily by the /@NABTn parameter on the OSRWATCH command. See the OSRWATCH documentation in topic OSRWATCH for more information. A value of 0 indicates "do not monitor the number of aborted transmissions". If the keyword OSRWATCH_NABT is not specified, the default value is 0. If OSRWATCH is not to be run in this station, this keyword does not apply. OSRWATCH_NDTO The OSRWATCH default threshold for the number of Data Link Control (DLC) time outs. If this threshold is exceeded, OSRWATCH generates a generic alert. This value may be overridden temporarily by the /@NDTOn parameter on the OSRWATCH command. See the OSRWATCH documentation in topic OSRWATCH for more information. A value of 0 indicates "do not monitor the number of time outs". If the keyword OSRWATCH_NDTO is not specified, the default value is 0. If OSRWATCH is not to be run in this station, this keyword does not apply. OSRWATCH_NBFX The OSRWATCH default threshold for the number of buffers exhausted. If this threshold is exceeded, OSRWATCH generates a generic alert. This value may be overridden temporarily by the /@NBFXn parameter on the OSRWATCH command. See the OSRWATCH documentation in topic OSRWATCH for more information. A value of 0 indicates "do not monitor the number of buffers exhausted". If the keyword OSRWATCH_NBFX is not specified, the default value is 0. If OSRWATCH is not to be run in this station, this keyword does not apply. OSRWATCH_NLGN The OSRWATCH default threshold for the number of users logged on. If this threshold is exceeded, OSRWATCH generates a generic alert. This value may be overridden temporarily by the /@NLGNn parameter on the OSRWATCH command. See the OSRWATCH documentation in topic OSRWATCH for more information. A value of 0 indicates "do not monitor the number of users logged on". If the keyword OSRWATCH_NLGN is not specified, the default value is 0. If OSRWATCH is not to be run in this station, this keyword does not apply. OSRWATCH_NDTI The OSRWATCH default threshold for the Data Link Control (DLC) inactivity timer (Ti) time outs. If this threshold is exceeded, OSRWATCH generates a generic alert. This value may be overridden temporarily by the /@NDTIn parameter on the OSRWATCH command. See the OSRWATCH documentation in topic OSRWATCH for more information. A value of 0 indicates "do not monitor the number of Ti time outs". If the keyword OSRWATCH_NDTI is not specified, the default value is 0. If OSRWATCH is not to be run in this station, this keyword does not apply. OSRWATCH_NDT1 The OSRWATCH default threshold for the Data Link Control (DLC) response timer (T1) time outs. If this threshold is exceeded, OSRWATCH generates a generic alert. This value may be overridden temporarily by the /@NDT1n parameter on the OSRWATCH command. See the OSRWATCH documentation in topic OSRWATCH for more information. A value of 0 indicates "do not monitor the number of T1 time outs". If the keyword OSRWATCH_NDT1 is not specified, the default value is 0. If OSRWATCH is not to be run in this station, this keyword does not apply. LAN_ADAPTER This keyword applies to IBM OS/2 LAN Requester stations only. Specifies the workstation adapter (primary or secondary) that LMU/2 NETBIOS applications such as LMUCMD and OSRWATCH are to use, or the station adapter the fault manager (AUECATCH) is to use when forwarding alerts via the LAN. This value is a 2-digit hexadecimal number and may be overridden temporarily by the /a parameter on the LMUCMD or OSRWATCH command. A value of 00 indicates the primary adapter; a value of 01 indicates the secondary adapter. If the keyword LAN_ADAPTER is not specified, the default value is 00. If LMU/2 NETBIOS applications, such as LMUCMD or OSRWATCH, are not to be run in this station, and the fault manager (AUECATCH) is not to forward alerts from this station, this keyword does not apply. SRVWATCH_SAVR The SRVWATCH default threshold for the server average response time. This threshold is in two parts, separated by a comma: o The response time threshold, in milliseconds o The (optional) count of consecutive collection intervals in which there is an excess, before generating an alert. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@SAVRms,cnt parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server average response time". If the keyword SRVWATCH_SAVR is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. SRVWATCH_SRBF The SRVWATCH default threshold for the server request-buffer-allocation failures. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@SRBFn parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server request buffer allocation failures". If the keyword SRVWATCH_SRBF is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. SRVWATCH_SBBF The SRVWATCH default threshold for the server big-buffer-allocation failures. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@SBBFn parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server big buffer allocation failures". If the keyword SRVWATCH_SBBF is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. SRVWATCH_TSES The SRVWATCH default threshold for the server total session count. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@TSESn parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server total session count". If the keyword SRVWATCH_TSES is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. SRVWATCH_TCON The SRVWATCH default threshold for the server total connection count. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@TCONn parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server total connection count". If the keyword SRVWATCH_TCON is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. SRVWATCH_TOPN The SRVWATCH default threshold for the server total open files count. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@TOPNn parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server total open files count". If the keyword SRVWATCH_TOPN is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. SRVWATCH_SSES The SRVWATCH default threshold for the server number of sessions in use by a single user. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@SSESn parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server number of sessions with a single user". If the keyword SRVWATCH_SSES is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. SRVWATCH_SCON The SRVWATCH default threshold for the server number of connections in use by a single user. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@SCONn parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server number of connections with a single user". If the keyword SRVWATCH_SCON is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. SRVWATCH_SOPN The SRVWATCH default threshold for the server number of file opens by a single user. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@SOPNn parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server number of file opens by a single user". If the keyword SRVWATCH_SOPN is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. SRVWATCH_SIDL The SRVWATCH default threshold for the server user session idle time. If this threshold is exceeded, SRVWATCH generates a generic alert. This value may be overridden temporarily by the /@SIDLn parameter on the SRVWATCH command. See the SRVWATCH documentation in topic SRVWATCH for more information. A value of 0 indicates "do not monitor the server maximum user session idle time". If the keyword SRVWATCH_SIDL is not specified, the default value is 0. If SRVWATCH is not to be run in this station, this keyword does not apply. BIND Identifies the location (drive and directory) of the LMU/2 database bind (.BND) files. If this workstation is not a managing system with database, this keyword does not apply. CHANGE_LOG Specifies the path and name of the file in which vital product data changes in the LMU/2 database will be recorded. If this workstation is not a managing system with database, this keyword does not apply. FILE_PATH Specifies the location used in the managing system as the central collection and transfer point for the output files from programs such as LMUGETCF. FAULT_TABLE Identifies the path and filename of the user-written alerts table. If this workstation is not a fault manager, this keyword does not apply. FM_FORWARDING_ADDR Identifies the Token-Ring Network adapter address to which the fault manager in this workstation (AUECATCH with option 2) is to forward alerts. If this workstation is not a fault manager (running AUECATCH with option 2), this keyword does not apply. SCHEDULE_LOG Identifies the path and file name for the log file written by the LMU/2 scheduler (LMUSTEP). If this workstation does not run the scheduler program, this keyword does not apply. SCHEDULE_FILE Identifies the path and file name for the user-defined schedule file used by the LMU/2 scheduler (LMUSTEP). If this workstation does not run the scheduler program, this keyword does not apply. SCHEDULE_GROUP_FILE Identifies the path and file name for the workstation groups definition file used by the LMU/2 scheduler (LMUSTEP). If this workstation does not run the scheduler program, this keyword does not apply. SCHEDULE_READ Identifies the frequency, in minutes, that the LMU/2 scheduler program (LMUSTEP) will check the schedule file for any schedule changes. If this workstation does not run the scheduler program, this keyword does not apply. ΓòÉΓòÉΓòÉ 6.7.3. CONFIG.SYS Statements ΓòÉΓòÉΓòÉ In each OS/2 station, update the CONFIG.SYS file to include the LAN Management Utilities/2 subdirectory in the PATH, LIBPATH, and DPATH search order. If data files such as USERVPD.DAT, CRITFILE.DEF, ADAPTERS.DEF, or the DINI-LINI-DPRG help (.HLP) or message (.MSG) files are located in a directory other than the LMU/2 subdirectory, include the directory for those files in the DPATH statement also. In each OS/2 managed station: o Include the IOPL=YES statement in the CONFIG.SYS file. The QUERYVPD.EXE program requires an I/O privilege level of 2 to operate; IOPL=YES grants that privilege level. o If the managed system is to be able to execute a SHUTDOWN command with the /b option, include the DEVICE=C:\LMU2\LMUIPL.SYS statement in the CONFIG.SYS file. Note: For IBM OS/2 LAN Requester stations, the customization program, LMUCUST, automatically updates the CONFIG.SYS file with these statements. In each IBM DOS LAN Requester managed station: o Additional NETBIOS resources may be needed by the LMU/2 DOS programs. Update the CONFIG.SYS file LAN Support Program device driver statements to include the additional NETBIOS resources. The additional NETBIOS resources are: RESOURCE AMOUNT NETBIOS Commands 1 NETBIOS Names 1 NETBIOS Sessions 1 For a detailed description of how to set the appropriate parameters, see the section on LAN Support Program information in the IBM LAN Technical Reference. o Optionally, update the CONFIG.SYS PATH statement to specify the location of the LMU/2 software. Otherwise, you may need to specify the drive and subdirectory on the command to execute a program. ΓòÉΓòÉΓòÉ 6.7.4. STARTUP.CMD Statements ΓòÉΓòÉΓòÉ If you want the LMU/2 managed, managing, and fault management functions started automatically when the OS/2 station is started, place the necessary START and DETACH statements in the STARTUP.CMD file or in a .CMD file called by STARTUP.CMD. Make sure the requester functions are started and running before issuing the START and DETACH statements for the LMU/2 functions. No START or DETACH statements are required for the administrator workstation function. For IBM OS/2 LAN Requester stations, the LMUCUST program places the statements for you automatically. These are the startup statements LMUCUST places in LMUSTART.CMD, by function: +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Γöé LMU/2 FUNCTION Γöé STARTUP STATEMENTS Γöé +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Γöé Fault reporter Γöé DETACH AUEPITCH.EXE Γöé +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Γöé Fault Manager Γöé START AUERECVR.EXE Γöé Γöé Γöé START AUECATCH.EXE Γöé +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Γöé Managed Γöé START LMUCLI.EXE Γöé +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Γöé Managing Γöé START LMUSRV.EXE Γöé Γöé Γöé DETACH AUEPITCH.EXE Γöé +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Note: For managing stations that are not to maintain an LMU/2 database, check the LMUSTART.CMD file to make sure the START LMUSRV.EXE command is START LMUSRV.EXE /r. At least one managing station in the network must maintain an LMU/2 database. DETACH AUEPITCH.EXE is not needed whenever the station contains the Managed function. Examples: +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Γöé LMU/2 FUNCTIONS IN A STATION Γöé STARTUP STATEMENTS Γöé +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Γöé Managed and managing Γöé START LMUCLI.EXE Γöé Γöé Γöé START LMUSRV.EXE Γöé +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ Γöé Managed and fault reporter Γöé START LMUCLI.EXE Γöé +ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ+ You may create or modify the STARTUP.CMD file to include a call to the LMUSTART.CMD file. Place the call somewhere after the statements that start the requester and that access the disk that contains the LMU/2 software. Make certain the LAN requester is running before issuing the call to LMUSTART.CMD. This is the call statement to use: CALL d:\LMU2\LMUSTART.CMD where d is the drive containing the LMU/2 software. If the contents of the STARTUP.CMD file are written in REXX, enclose the call statement in single quotes: 'CALL d:\LMU2\LMUSTART.CMD' Restart the computer after running LMUCUST, to activate the CONFIG.SYS and STARTUP.CMD changes. Note: If the station is a fault manager, see the section Special Considerations for Fault Managers before restarting the computer. ΓòÉΓòÉΓòÉ 6.7.5. Copying Required Files ΓòÉΓòÉΓòÉ If an OS/2 system is to be able to execute a SHUTDOWN command with the /b option (re-IPL), copy the LMUIPL.SYS file to C:\LMU2 (required location) in that computer. See CONFIG.SYS Statements for the DEVICE statement to add to the CONFIG.SYS file in that computer. This requirement does not apply to Novell NetWare file servers. Note: For IBM OS/2 LAN Requester stations, the customization program, LMUCUST, automatically copies LMUIPL.SYS to the C:\LMU2 directory and updates the CONFIG.SYS file with the necessary statements. ΓòÉΓòÉΓòÉ 6.7.6. Other Software Installation ΓòÉΓòÉΓòÉ If you plan to use PERFCAP or PERFWACH, you must install the IBM System Performance Monitor/2 (SPM/2) on those managed stations. ΓòÉΓòÉΓòÉ 6.7.7. Creating the Database ΓòÉΓòÉΓòÉ The first time LMUSRV is started in a system, it automatically creates the LMU/2 database, using the default name and location if no parameters are specified. On those managing systems where you do not want the database, be sure to specify the /r option when you start LMUSRV. ΓòÉΓòÉΓòÉ 6.7.8. Handling Generic Alerts ΓòÉΓòÉΓòÉ Before executing the fault manager component of the LAN Management Utilities/2, you must create the alerts table file that identifies the generic alerts you want the fault manager to process. Use a text editor such as the OS/2 System Editor to define the table (see User-Defined Table for the table format). Additionally, you must decide where you want the fault manager to forward generic alerts that do not match any entry in the table, or that have reached the notification threshold specified in the table. You may choose to forward generic alerts to NetView or to the IBM LAN Network Manager. See Fault Management for details on how to implement your choice. ΓòÉΓòÉΓòÉ 7. Command Transport ΓòÉΓòÉΓòÉ LAN Management Utilities/2 (LMU/2) programs are started and driven through command line interfaces. The following section tells you how to start the LMU/2 command transport. The command transport enables an administrator workstation to solicit information from, and direct the activities of, a managed system. Note: User-written applications can be invoked remotely using the transport mechanism and can collect information, but will be unable to use the transport mechanism to have the response information recorded in the database. Continue on the next page of this section. ΓòÉΓòÉΓòÉ 7.1. Starting the Transport ΓòÉΓòÉΓòÉ Starting a managing system: IBM OS/2 LAN Requester or Novell NetWare Requester for OS/2, as approppriate, must be running in the computer. If the managing system maintains an LMU/2 database, the system must be logged on as either a local administrator or a domain administrator. Start the managing system transport by starting the LMUSRV command (START LMUSRV) in the LAN server that is the managing computer. LMUSRV is discussed in topic LMUSRV. Starting an OS/2 managed system: IBM OS/2 LAN Requester or Novell NetWare Requester for OS/2, as approppriate, must be running in the computer. Start the managed system transport by starting the LMUCLI command (START LMUCLI) in the LAN requester that is the managed computer. LMUCLI is discussed in topic LMUCLI. Starting a DOS managed system: IBM DOS LAN Requester or Novell NetWare Requester for DOS, as appropriate, must be running in the computer. Issue the LMUDOSHB command to produce an initial heartbeat. Collect vital product data and send the data to the managing system by issuing the QDOSVPD command in the DOS station that is the managed computer. QDOSVPD is discussed in topic QDOSVPD. Starting a database machine: See the instructions for starting a managing system, above. Continue on the next page of this section. ΓòÉΓòÉΓòÉ 7.2. Using the Transport ΓòÉΓòÉΓòÉ Remote command execution: After the managing and managed systems have been started, issue the LMUCMD command from the administrator workstation to an OS/2 managed system, to request the managed system to execute a command or system management application. The command or program is started using the standard OS/2 command line interface. Depending on the options specified for LMUCMD, LMU/2 can relay the console output back to the administrator workstation. LMUCMD is discussed in topic LMUCMD. Note: DOS managed systems cannot respond to remote command requests. Continue on the next page of this section. ΓòÉΓòÉΓòÉ 7.3. Transport Commands ΓòÉΓòÉΓòÉ The transport commands are: o LMUSRV, in a managing system o LMUCLI, in an OS/2 or Novell NetWare Server managed system o LMUCMD, in an administrator workstation. ΓòÉΓòÉΓòÉ 7.3.1. LMUSRV ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUSRV ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /A[[C][H][S]] ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Ladapter ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Ppath ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Xuser-exit ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇ /CcommentΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇΓöÇ /Ddrive ΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇΓöÇ /Nname ΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /R ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Help information /A[[C][H][S]] Enable alerts: [C]hange log, [H]eartbeat, [S]erver; a null string enables all alerts; default is no alerts /Ladapter NETBIOS adapter; range is 0 to 255 (where 0 is primary adapter, 1 is secondary adapter, etc.); default is value specified for LAN_ADAPTER key in LMU.INI, or 0 if not in LMU.INI /Ppath Drive and path to write transfered files; default is value specified for FILE_PATH key in LMU.INI, or root of boot drive if not in LMU.INI /Xuser-exit User exit (program w/arguments) to be invoked when an alert condition is detected; no default /Ccomment Database comment; default is "LAN Management Utilities/2" /Ddrive Database drive; default is the drive where OS/2 Database Manager is installed /Nname Database name; default is LMU2 /R Remote database; default is local database LMUSRV Command Line Help Information LMUSRV provides command transport in the managing system, and creates and updates an LMU/2 database. Maintaining the database is the default for a managing system and requires that IBM OS/2 Database Manager be installed. Use the /r option to prevent LMUSRV from creating a database. LMUSRV permits a managing system to receive and forward LMUCMD commands from other managing systems to managed systems. This function can be used by managing systems that do not have Database Manager installed or in configurations where the database resides on another managing system. The LMU/2 database contains: o Vital product data collected by the QUERYVPD or QDOSVPD programs on a managed system. o Performance information collected by the PERFCAP program on a managed system. Refer to LAN Management Utilities/2 Database Tables for a complete description of the LMU/2 database. The /a option controls which kind of alerts LMUSRV may generate. (See LMUSRV Alerts for a discussion of the kinds of alerts.) The /r option controls whether LMUSRV uses a local database or a remote database. The /c, /d, and /n options are used to control the comment, drive, and name (respectively) of the LMU/2 database. If used, /r takes precedence over any /c, /d, /n, or /ac options. o The /a (alerts) option specifies which alerts LMUSRV may generate. The /a is followed immediately by any combination of c, h, and s. c - Enable configuration change alerts. h - Enable heartbeat alerts. s - Enable server (LMUSRV) alerts. To enable all alerts, specify /achs or just /a (/a with no operands). If the /a option is omitted, LMUSRV generates no alerts. o The /ladapter (LAN adapter) option specifies which LAN adapter in this workstation LMUSRV is to use for NETBIOS communications. The valid values for adapter are 0 to 255, in decimal (/l0 to /l255). Use /l0 for the primary adapter, /l1 for the secondary adapter, and so forth. o The /ppath option specifies the location used in the managing system as the central collection and transfer point for the output files from programs such as LMUGETCF. o The /xuserexit option specifies the user program and arguments to be invoked when an LMUSRV alert condition is detected. If the program is not in the current directory where LMUSRV is executing, specify the full drive, path for the program. If any part of the userexit information contains blanks (such as blank separaters between the arguments), enclose the entire userexit string in double quotes: /x"drive\path\program.ext arg1 arg2 arg3" o The /c (database comment) option is an optional 30-character description to be stored in the database directory entry when a new database is created. If the /c option is not specified, the database comment defaults to "LAN Management Utilities/2". Use double quotes to include embedded blanks. For example: LMUSRV /c"LMU Test Database" o The /d (database drive) option is a single letter specifying the drive where the database is to be created. The default is to create the database on the drive where Database Manager Database Services is installed. Example: LMUSRV /de creates the database on the E: drive. Notes 1. The drive may be a shared disk on the LAN. 2. The drive letter may be an alias for a subdirectory. Warning: Use this option with caution. If the database is created on a shared disk on the LAN, and another IBM Database Manager is on the machine that houses the physical drive, the directory for the other Database Manager will not be updated to reflect the existence of the LMU/2 database. Not only will the other Database Manager be unable to access the LMU/2 database that is on its physical disk, the other Database Manager may destroy the LMU/2 database inadvertently. o The /n (database name) option is the 8-character name of the LMU/2 database to be created, if it does not exist, and updated. If the /n option is not specified, the database name defaults to LMU. o The /r option indicates that this managing system does not maintain an LMU/2 database. To cause LMUSRV to create and maintain an LMU/2 database, omit the /r option (note that Database Manager must be installed). Every managing system with database must omit the /r option on the LMUSRV command. Note: If an LMU/2 database already exists, LMUSRV uses that database instead of observing the /c and /d parameters. ΓòÉΓòÉΓòÉ 7.3.1.1. Change Log ΓòÉΓòÉΓòÉ The change log is produced automatically by LMUSRV on a database machine (managing system with database). LMUSRV reads the LMU/2 database and it records, per workstation, the differences in vital product data between successive reportings for the workstation. No change log entry is made for a workstation if no differences are detected. New entries are appended to the bottom of the file. The time and date in the entries reflect when the information was captured; they do not reflect when the information changed. The location and name of the change log are specified in the managing system with database (database machine) LMU.INI file. You can change the name or location by modifying the CHANGE_LOG parameter in the LMU/2 control file and running the LINI program to update the LMU.INI file. If no change log name and location are specified in the LMU.INI file, detected configuration changes are not recorded. A sample change log is in topic Sample Change Log. ΓòÉΓòÉΓòÉ 7.3.1.2. LMUSRV Alerts ΓòÉΓòÉΓòÉ LMUSRV can create generic alerts for the conditions identified below. Note: AUEPITCH must be started (detached) for the alerts to be sent to the fault manager. To suppress any of these kinds of alerts, omit the corresponding operand of the /a option on the LMUSRV command. To suppress all these alerts, omit the /a option entirely. Configuration changes (change log) On a managing system with database, LMUSRV creates a generic alert (LMU0905I) whenever it detects a change in the configuration information for a workstation and makes an entry in the change log. Heartbeat As a result of the LMUCLI heartbeat function (see Heartbeat), LMUSRV creates a generic alert on behalf of a managed system and sends it to the fault manager for the following conditions: o LMUCLI in a managed system is started (LMU0902I) o LMUCLI in a managed system does not report (LMU0904E) o LMUCLI in a managed system is restarted (LMU0902I) o LMUCLI in a managed system is terminated (LMU0903I). Server LMUSRV also generates initialization and termination alerts when LMUSRV itself is started or stopped (LMU0900I and LMU0901I, respectively). ΓòÉΓòÉΓòÉ 7.3.2. LMUCLI.EXE ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUCLI ΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Options: ? Help information LMUCLI Syntax Note that LMUCLI has no command options. LMUCLI provides the command receiving function to the managed system. LMUCLI must be started and running in any workstation that is to be the target of the LMUCMD command, before the workstation can receive the command and respond to it. In addition, during initialization LMUCLI automatically enables (detaches) the fault reporter function (AUEPITCH) in the managed system. LMUCLI runs as an "invisible" OS/2 Presentation Manager application. The end workstation user will not be able to detect its presence through ordinary means (and possibly cancel it). To determine if LMUCLI is running in the station, use the LMUQUERY command. See LMUQUERY for details about the LMUQUERY command. ΓòÉΓòÉΓòÉ 7.3.2.1. Heartbeat ΓòÉΓòÉΓòÉ This feature of LMUCLI causes alerts to be generated indicating the status of LMUCLI (see LMUSRV Alerts). With this function: 1. When LMUCLI starts, it sends a message to LMUSRV in the managing system, telling the managing system to expect messages indicating that all is well. The interval for the messages is specified in the managed system LMU.INI file. If the interval specified is zero (0), this is the only message sent until LMUCLI terminates. 2. If the interval is non-zero, LMUCLI sends an "LMUCLI is well" message to the managing system at the intervals specified. 3. Whenever LMUCLI terminates, it sends a message to the managing system telling the managing system not to expect any more messages. If the managing system has been notified to expect messages regularly and it does not receive an "I am well" message within the required time, LMUSRV in the managing system generates a generic alert and sends it to the fault management system. The heartbeat interval in LMU.INI is customized through the LMU/2 control file and the LINI program. The heartbeat interval parameter in the LMU/2 control file is PULSE_RATE. ΓòÉΓòÉΓòÉ 7.3.2.2. LMUCLI Alerts ΓòÉΓòÉΓòÉ Alerts are generated by LMUSRV on behalf of LMUCLI. Heartbeat: As a result of the LMUCLI heartbeat function, LMUSRV in the managing system generates a generic alert on behalf of the managed system and sends it to the fault manager for the following conditions: o LMUCLI in a managed system is started (LMU0902I). o LMUCLI in a managed system does not report (LMU0904E). o LMUCLI in a managed system is restarted (LMU0902I). o LMUCLI in a managed system is terminated (LMU0903I). ΓòÉΓòÉΓòÉ 7.3.3. LMUCLI.NLM ΓòÉΓòÉΓòÉ LMUCLI.NLM enables the Novell NetWare Server to become a managed system. Like the OS/2 LMUCLI.EXE program, LMUCLI.NLM performs the following functions: o Sends heartbeats to its managing system o Receives and runs remote commands from an LMU/2 administrator workstation. The commands can be any commands that can be issued from the NetWare system console and that do not require user response. Unlike LMUCLI.EXE, LMUCLI.NLM is not able to relay the command output back to the administrator workstation. ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUCLI ΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Options: ? Help information LMUCLI.NLM Syntax Note that LMUCLI has no command options. LMUCLI provides the command receiving function to the managed system. LMUCLI must be started and running in any workstation that is to be the target of the LMUCMD command, before the workstation can receive the command and respond to it. ΓòÉΓòÉΓòÉ 7.3.3.1. Heartbeat (NLM) ΓòÉΓòÉΓòÉ This feature of LMUCLI.NLM causes alerts to be generated indicating the status of LMUCLI.NLM (see LMUSRV Alerts). With this function: 1. When LMUCLI starts, it sends a message to LMUSRV in the managing system, telling the managing system to expect messages indicating that all is well. The interval for the messages is specified in the NetWare Server bindery. If the interval specified is zero (0), this is the only message sent until LMUCLI terminates. 2. If the interval is non-zero, LMUCLI sends an "LMUCLI is well" message to the managing system at the intervals specified. 3. Whenever LMUCLI is unloaded it sends a message to the managing system telling the managing system not to expect any more messages. If the managing system has been notified to expect messages regularly and it does not receive an "I am well" message within the required time, LMUSRV in the managing system generates a generic alert and sends it to the fault management system. The heartbeat interval property (PULSE RATE) in the bindery is set during server customization through the LMUBIND.CTL file. After server customization is complete, LMULOAD.NLM can be used to view or modify the heartbeat interval value. ΓòÉΓòÉΓòÉ 7.3.3.2. LMUCLI.NLM Alerts ΓòÉΓòÉΓòÉ Alerts are generated by LMUSRV on behalf of LMUCLI.NLM. Heartbeat: As a result of the LMUCLI heartbeat function, LMUSRV in the managing system generates a generic alert on behalf of the managed system and sends it to the fault manager for the following conditions: o LMUCLI in a managed system is started (LMU0902I). o LMUCLI in a managed system does not report (LMU0904E). o LMUCLI in a managed system is restarted (LMU0902I). o LMUCLI in a managed system is terminated (LMU0903I). ΓòÉΓòÉΓòÉ 7.3.4. LMUCMD ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUCMD ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇ target ΓöÇΓöÇΓöÇ command-string ΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇ /Aadapter ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ /Mmanaging-system ΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Q ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /Rrelay-adapter ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /S ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇ /Ttime-out ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Help information /Aadapter NETBIOS adapter; range is 0 to 255 (where 0 is primary adapter, 1 is secondary adapter, etc.); default is value specified for LAN_ADAPTER key in LMU.INI or 0 if not in LMU.INI /Mmanaging-system Managing system to use for broadcast; default is value specified for MANAGING_SYSTEM key in LMU.INI /Q Quiet (do not relay output); default for broadcast /Rrelay-adapter LAN adapter used by target workstation when relaying output back to this workstation via NETBIOS; range is 0 to 255 (where 0 is primary adapter, 1 is secondary adapter, etc.); if not specified, the target workstation will determine relay adapter /S Suppress message/line number prefix from relayed output; default is to prefix relayed output /Ttime-out Output wait time out interval; range is 1 to 120 seconds; default is to wait indefinitely target Target workstation; valid formats: For IBM OS/2 LAN Server or OS/2 LAN Requester: - computer-name - * (broadcast to domain of managing system) - *MANAGED (broadcast to managing system's managed systems) For Novell NetWare server or NetWare Requester for OS/2: - [network-number]:node-address - server-name. - [server-name].user-name - [network-number]:* (broadcast to specified NetWare network) - *MANAGED (broadcast to managing system's managed systems) command-string Command to execute on target workstation(s) LMUCMD Command Line Help Information Important LMUCMD can be issued only from an administrator workstation. If the administrator workstation is an IBM LAN Requester, the administrator workstation checks that it is a domain administrator to the managing system before forwarding the command. If the administrator workstation is a Novell NetWare Requester for OS/2, the administrator workstation checks that it is logged in to the NetWare server as a supervisor equivalent before forwarding the command. LMUCMD uses the LMU/2 transport to pass a command string (command-string) to the OS/2 target computer for execution. The command string may be any valid command that can be issued from a command line, including another LMUCMD command. Note that the response information returned is from the first command only in the string. In order for command-string to be received at the target computer, the target computer must be running the LMUCLI transport software. The target computer named can be any requester ID reachable on the network; If the target computer cannot be located in the network or if the target computer is not running LMUCLI, command-string is not delivered and LMUCMD terminates with an error. LMUCMD has the ability to redirect standard output (STDOUT) and standard error (STDERR) from the OS/2 managed system back to the issuing administrator workstation. Response information that would normally appear on the managed system display, for example, will appear on the administrator workstation display. Note: LMUCMD will truncate any redirected STDOUT or STDERR lines to a length of 512 bytes. Parameters: o The ? option produces the help panel. o The /aadapter (LAN adapter) option specifies which LAN adapter in this workstation LMUCMD is to use for NETBIOS communications. The valid values for adapter are 0 to 255, in decimal. Use 0 for the primary adapter, 1 for the secondary adapter, and so forth. o The /m option specifies a managing system to use to route the broadcast command to the target computer; if the command is not broadcast, the /m option does not apply. The name of the managing system immediately follows the /m, with no intervening space. If the managing system is an IBM LAN Requester, the name must be the requester ID of the managing system (identified by COMPUTERNAME in the IBMLAN .INI file in the managing system). If the managing system is a Novell NetWare Requester for OS/2, the name must be the internetwork address ([network number]:node-address). If the /m option is not specified, the command is routed through the managing system identified in the administrator workstation LMU.INI file. o The /q option suppresses redirection of the response information back to the administrator workstation, and causes the administrator workstation to return to the command line prompt immediately. The /q option is invoked automatically if the command is broadcast (see the "target" parameter). o The /rrelay-adapter option specifies which LAN adapter on the target workstation to use to relay output back to this administrator workstation. (When the target workstation has multiple LAN adapters, each of which is connected to a different LAN, this option allows you to direct the output onto the LAN to which this administrator workstation is attached.) The relay-adapter is from one to three decimal digits. Valid values are 0-255, where 0 represents the primary adapter, 1 represents the secondary adapter, and so forth. If the /r option is not specified, the target workstation determines which adapter to use to relay output back to the administrator workstation. o The /t option is not applicable to Novell NetWare targets. The /t option specifies the wait time for receipt of each line of response data. The time, in seconds, immediately follows the /t, with no intervening space. The range is 1-120 seconds. The recommended time is 60 seconds or more, to allow for travel on the network. The timer starts as soon as the command is sent to the managing system, and starts over again for each line of data being returned. If the timer expires, the administrator workstation returns to the command line prompt; any remaining responses from the issued command are not displayed. If /t is not specified, the default is to wait indefinitely. o The target option specifies the managed computer or computers that are to execute the command specified by command-string. If the managed computer is an IBM LAN Requester or LAN Server, target is one of the following: - The name of the managed computer that is to execute the command specified by command-string. The name must be the requester ID of the target computer (identified by COMPUTERNAME in the IBMLAN.INI file in the target computer). - An asterisk (*). The asterisk specifies broadcasting to all managed systems in the managing system's domain. The command is sent to the managing system specified (by the /m option or the administrator workstation LMU.INI file), for routing to the managed systems. - An asterisk followed by the word "managed" (*MANAGED). The *MANAGED specifies broadcasting across domains to all managed systems reporting to the managing system (that is, to all managed systems that are executing LMUCLI and for whom the managing system has processed a heartbeat). When the managed system is a Novell NetWare Requester for OS/2, target is one of the following: - The NetWare internetwork address of the computer, which consists of the network number (optional) followed by a colon and the NetWare node address of the computer. The network number may be omitted or replaced by a zero (0); if the network number is omitted, zero is assumed. - The server name (optional) followed by a period and the NetWare user name for the computer. This address must be unique or unambiguous. If the server name is omitted, LMUCMD checks all servers to which the administrator workstation is attached, to find the user name. If the server name is specified, it must be one to which the administrator workstation is attached. - The network number (optional) followed by a colon and an asterisk (*). The network number:* specifies broadcasting to the specified NetWare network. If the network number is not specified, the command is broadcast to the local network for the administrator workstation. - An asterisk followed by the word "managed" (*MANAGED). The *MANAGED specifies broadcasting across networks to all managed systems reporting to the managing system (that is, to all managed systems that are executing LMUCLI and for whom the managing system has processed a heartbeat). Note that when broadcasting is used, the /q option is invoked automatically (command responses are not returned to the administrator workstation). o Command-string is any valid command string to be executed on the target computer. A valid command string is one that could be entered from the command line of the target computer, and that does not require user response at the console of the target computer. If broadcasting or the /q option is used (response information is not returned to the administrator workstation), LMUCMD functions as follows: - You may use standard OS/2 redirection (< or >) to redirect the output (or input) of the command string to a file or other device. If redirection is used, the entire redirection sequence must be placed in double quotes (see the example below). This is the only valid use of quotes in the command string. Example: lmucmd /q USER12 net who ">e:\save.out" --results in net who >e:\save.out --at USER12. Note that redirection is standard OS/2 redirection to a file or other device; you cannot use redirection to return output to the issuing administrator workstation. - The window that is opened at the target computer is automatically closed when the command has executed. To retain the window, specify start /k as the first part of the command string. (See the example in Examples, below.) Note: LMUCMD adds or retains double quotes around command-string parameters that: - Are null ("") - Contain one or more blanks. Use of null parameters or blanks in the LMUCMD command-string when using standard OS/2 redirection may produce unexpected results. Examples: ">c:\file.out" is accepted "> c:\file.out" may not work as expected. Examples: Example 1 lmucmd /s 0:10005a8d7080 type config.sys produces the following output at the administrator workstation display (truncated at the right in this sample): IBM LAN Management Utilities/2 Version 2.00 5799-PLX (C) Copyright IBM Corp. 1991, 1992. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. LAN Management Utilities/2 Maintenance Level IC03528 LMU9010I Command sent to target 0:10005A8D7080; waiting for output LMU9024I Output: IFS=C:\OS2\HPFS.IFS -C:64 PROTSHELL=C:\OS2\PMSHELL.EXE C:\OS2\OS2.INI C:\OS2\OS2SYS.INI C:\OS2\CMD.EXE SET COMSPEC=C:\OS2\CMD.EXE LIBPATH=.;C:\;C:\OS2\DLL;C:\MUGLIB\DLL;C:\SQLLIB\DLL;C:\CMLIB\DLL;C:\IBMLAN\NETLIB;C:\NETWARE;C:\PRGMR01\DLL;C:\PRGMR01\PMLIB;C:\P SET PATH=C:\;C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\MUGLIB;C:\SQLLIB;C:\CMLIB;C:\IBMLAN\NETPROG;L:\OS2;C:\PRGMR01;C:\PRGMR01\BGIMA SET DPATH=C:\;C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\MUGLIB\DLL;C:\CMLIB;C:\IBMLAN\NETPROG;C:\NETWARE;C:\PRGMR01;C:\PRGMR01\SOURCE SET BGIMAGE_PATH=C:\PRGMR01\BGIMAGE\BMP(HPFS) SET PROMPT=$i[$p] SET HELP=C:\OS2\HELP; BUFFERS=60 IOPL=YES MAXWAIT=3 MEMMAN=SWAP,MOVE,NOSWAPDOS PROTECTONLY=NO SWAPPATH=C:\OS2\SYSTEM 512 THREADS=255 COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS DEVINFO=SCR,BGA,C:\OS2\VIOTBL.DCP DEVICE=C:\CMLIB\R0CSDD.SYS SET VIDEO_DEVICES=VIO_IBM8514A SET VIO_IBM8514A=DEVICE(BVHVGA,BVH8514A) DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MSPS202.SYS DEVICE=C:\OS2\MOUSE.SYS TYPE=MSPS2$ DEVICE=C:\OS2\PMDD.SYS SET KEYS=ON SET BOOKSHELF=C:\OS2\BOOK; SHELL=C:\OS2\COMMAND.COM /P BREAK=OFF FCBS=16,8 RMSIZE=640 DEVICE=C:\OS2\EGA.SYS DEVICE=C:\OS2\DOS.SYS DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP CODEPAGE=437,850 DEVICE=C:\CMLIB\LANDD.SYS DEVICE=C:\CMLIB\TRNETDD.SYS CFG=C:\CMLIB\MXMPUS6.CFG RUN=C:\CMLIB\ACSTRSYS.EXE DEVICE=C:\CMLIB\NETBDD.SYS CFG=C:\CMLIB\MXMPUS6.CFG DEVICE=C:\CMLIB\RDSLANDD.SYS LOG=ON SET QRWDR=C: SET QRWINST=C:\SQLLIB DEVICE=C:\IBMLAN\NETPROG\RDRHELP.SYS IFS=C:\IBMLAN\NETPROG\NETWKSTA.SYS /I:C:\IBMLAN DEVICE=C:\PRGMR01\LMUIPL.SYS SET VPD=SYNC REM --- NetWare Requester statements BEGIN --- DEVICE=C:\NETWARE\LSL.SYS RUN=C:\NETWARE\DDAEMON.EXE DEVICE=C:\NETWARE\CMGRLAN.SYS DEVICE=C:\NETWARE\ROUTE.SYS DEVICE=C:\NETWARE\IPX.SYS DEVICE=C:\NETWARE\SPX.SYS RUN=C:\NETWARE\SPDAEMON.EXE rem DEVICE=C:\NETWARE\NMPIPE.SYS rem DEVICE=C:\NETWARE\NPSERVER.SYS rem RUN=C:\NETWARE\NPDAEMON.EXE NP_COMPUTERNAME DEVICE=C:\NETWARE\NWREQ.SYS IFS=C:\NETWARE\NWIFS.IFS RUN=C:\NETWARE\NWDAEMON.EXE rem DEVICE=C:\NETWARE\NETBIOS.SYS rem RUN=C:\NETWARE\NBDAEMON.EXE rem RUN=C:\NETWARE\NWSPOOL.EXE REM --- NetWare Requester statements END --- Return code = 0 LMU9021I End-of-data Example 2 lmucmd /s mxmpus6 echo path = ^%path^% produces the following output at the administrator workstation display (truncated at the right in this sample): IBM LAN Management Utilities/2 Version 2.00 5799-PLX (C) Copyright IBM Corp. 1991, 1992. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. LAN Management Utilities/2 Maintenance Level IC03528 LMU9010I Command sent to target MXMPUS6; waiting for output LMU9024I Output: path = C:\;C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\MUGLIB;C:\SQLLIB;C:\CMLIB;C:\IBMLAN \NETPROG;L:\OS2;C:\PRGMR01;C:\PRGMR01\BGIMAGE;C:\PRGMR01\CODEVIEW;C:\PRGMR01\P MLIB;C:\PRGMR01\TOGGLE;C:\PRGMR01\DUMP;C:\PRGMR01\PKWARE;C:\PRGMR01\RAM;E:\BAT CH;E:\UTILITY;E:\XQ4LIB\SPM2;E:\TOOLKT12\BIN;E:\IBMC2\BIN;X:\;Y:\;Z:\; Return code = 0 LMU9021I End-of-data ΓòÉΓòÉΓòÉ 8. Management Applications (OS/2) ΓòÉΓòÉΓòÉ Purposes The following section describes the types of LAN Management Utilities/2 (LMU/2) management applications and the programs that are in each. The table in topic Will It Run in My Station? identifies the requesters and operating systems under which the applications run. Gathering Vital Product Data To gather vital product (configuration) data, use: QUERYVPD on a managed OS/2 station. QUERYVPD is discussed in topic QUERYVPD. To gather OS/2 Communications Manager configuration data, use: LMUGETCF on a managed OS/2 station. LMUGETCF is discussed in topic LMUGETCF. Monitoring Performance on the Network To monitor workstation performance on the network, use: PERFCAP to collect workstation performance data from the IBM System Performance Monitor/2 (SPM/2) product and send the collected information to a managing station. This data can be used for trending and capacity planning. PERFCAP is discussed in topic PERFCAP. PERFWACH to collect performance data for a workstation from the IBM System Performance Monitor/2 (SPM/2) product, analyze the collected data for selected conditions, and send generic alerts to the fault management system when those conditions occur. This provides event monitoring and alert generation for specific workstations. PERFWACH is discussed in topic PERFWACH. To monitor IBM NETBIOS statistics, use: OSRWATCH to monitor the set of workstations (adapters) logged on to a specified IBM LAN server for NETBIOS status, and to send generic alerts to the fault management system when specific conditions occur. This provides event monitoring and alert generation for a set of workstations. OSRWATCH is discussed in topic OSRWATCH. To monitor server performance, use: SRVWATCH to monitor an IBM OS/2 LAN server for average response time and buffer allocation failures, and to send generic alerts to the fault management system when specific conditions occur. This provides event monitoring and alert generation for a single server. SRVWATCH is discussed in topic SRVWATCH. To monitor Novell NetWare Requesters, use: IPXWATCH to monitor the statistics for Novell's Internetwork Packet Exchange (IPX) protocol in the OS/2 workstation in which IPXWATCH is running, and to send generic alerts to the fault management system when specific conditions occur. IPXWATCH is discussed in topic IPXWATCH. To monitor application programs in a workstation, use: APPWATCH to monitor how many instances of specified application programs are loaded into memory in the OS/2 workstation in which APPWATCH is running, and to send generic alerts to the fault management system when specific violations occur. APPWATCH is discussed in topic APPWATCH. Fault Management To handle local fault conditions or forward the alerts to IBM LAN Network Manager or IBM NetView, install these modules and start the executable programs: AUEUSRGA in the OS/2 client computer to generate local alerts. AUEUSRGA is discussed in topic AUEUSRGA. AUEPITCH in the client computer to direct local alerts to the fault manager system in a managing computer. AUEPITCH is discussed in topic AUEPITCH. AUECATCH in the fault manager computer to intercept the alerts. AUECATCH is discussed in topic AUECATCH. AUERECVR in the fault manager computer to respond to the alerts. A user-defined table identifies which alerts to handle locally, what actions to take, and which alerts to forward to NetView or the IBM LAN Network Manager. To send an alert to the fault manager after a virus-checking program detects a potential virus in a workstation, use: VIRALERT on a managed OS/2 station. An operator or user-written REXX program or .CMD file must determine when to run VIRALERT. VIRALERT is discussed in topic VIRALERT. To send a message to a workstation user as a result of an alert, use: LMUPOPUP in the command string of an entry in the alerts table, to display a popup window on the target workstation. LMUPOPUP is discussed in topic LMUPOPUP. To contact someone by electronic pager as a result of an alert condition, use: LMUPAGER in the command string of an entry in the alerts table, to send a message to a designated pager. LMUPAGER is discussed in topic LMUPAGER. LMUPAGE from the command line of an OS/2 workstation, to generate an alert manually that will trigger LMUPAGER. LMUPAGE is discussed in topic LMUPAGE. Query/Terminate To check whether an LMU/2 fault management, client, or server module is running in a workstation, or to terminate any of those modules in a workstation, use: LMUQUERY in the workstation to query or terminate AUEPITCH, AUECATCH, AUERECVR, LMUCLI, LMUGUI, or LMUSRV. LMUQUERY is discussed in topic LMUQUERY. To shut down an OS/2 workstation, particularly in the event of impending power loss, use: SHUTDOWN to shut down in an orderly manner all functions in a managed station. SHUTDOWN is discussed in topic SHUTDOWN. Using Profile Services To modify the system profile (OS2SYS.INI), the user profile (OS2.INI), or the LAN Management Utilities/2 profile (LMU.INI), or to create or modify any other true .INI file, use: DPRG to convert the Desktop Manager Program and Group information from a user profile, such as OS2.INI, to a text file of commands. The file can then be modified with a text editor. DPRG is discussed in topic DPRG. DINI to convert the run-time information for a program from a user profile (such as OS2.INI), from the system profile (OS2SYS.INI), or from any other named profile, to a text file of commands. The file can then be modified with a text editor. DINI is discussed in topic DINI. LINI to use a text file of commands (such as produced by DPRG or DINI and then modified) to update OS2SYS.INI, OS2.INI, or any other true .INI file, or to create a .INI file. LINI is discussed in topic LINI. ΓòÉΓòÉΓòÉ 8.1. Vital Product Data ΓòÉΓòÉΓòÉ Vital Product Data consists of configuration data about the workstation. To gather configuration data about an OS/2 workstation, see QUERYVPD. To see the configuration data tables in the LMU/2 database, see the topic LMU/2 Database Tables. ΓòÉΓòÉΓòÉ 8.1.1. QUERYVPD.EXE ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ QUERYVPD ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ +O[filespec] ΓöÇΓöñ ΓööΓöÇΓöÇ +Wpath ΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +A ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +P ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +Q ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓöÿ Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +D ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +S ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +R[destination] ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ -S ΓöÇΓöÿ Option Description: ? Displays this help panel. +A Displays the recognized Micro Channel adapters. +D Provides a more detailed description of most items within each category. (Example: ROM and RAM memory addresses by adapter). +S Provides SYSLEVEL file processing (searching and reporting). +O[filespec] Allows the redirection of display to QUERYVPD.DAT in current directory. Optional 'filespec' overrides filename and location to receive report. +P Pauses the display after each screen of output. +Q Turns off display of copyright information. +R[destination] Transmits vital product data to the LMU/2 managing system with database. Optional 'destination' (1 to 21 characters) specifies a computer name or internetwork address. (default: MANAGING_SYSTEM_WITH_DATABASE). Note: All categories of data are collected. -S Suppresses SYSLEVEL file processing (See +R option). +Wpath Specifies the location of the QUERYVPD working directory QUERYVPD Syntax The QUERYVPD program collects vital product data (configuration information) about the OS/2 machine in which it is executing. It is designed to be run both as a standalone utility and as part of LMU/2. When QUERYVPD is run, vital product data can be displayed at the console, redirected to a file, or sent from the managed system to a database machine and stored in an LMU/2 database. Data from the following optional user-defined files is included in the vital product data captured by QUERYVPD: o USERVPD.DAT o ADAPTERS.DEF o CRITFILE.DEF When QUERYVPD is initiated by the LMUCMD command, the vital product data console display can be redirected from the managed system back to the administrator workstation console. Vital Product Data Tables identifies the vital product data recorded by the LMU/2 database. Options: o The ? option produces the help panel. o The +a option displays the list of Micro Channel* adapters recognized by the QUERYVPD program. This includes the adapters identified in the ADAPTERS.DEF file. o The +d option provides additional, more detailed, information to the QUERYVPD console output, such as the following: - More detailed memory and disk information - More detailed logical disk information - POS data (Micro Channel machine only) - Planar ID (Micro Channel machine only) - The location of the CRITFILE.DEF file and USERVPD.DAT file used, if the files were found. o The +s option produces SYSLEVEL information (information from any program-associated SYSLEVEL.xxx file). Use this option to obtain information about the OS/2 operating system maintenance levels in the workstation, for example. o The +r option redirects the QUERYVPD output to a managing system with database (database machine), for inclusion in an LMU/2 database. All categories of data are collected. Destination is optional but, if used, must be one of the following: - For an IBM OS/2 LAN Requester, the requester ID of the database machine (COMPUTERNAME in the IBMLAN.INI file in the database machine) - For a Novell NetWare Requester for OS/2, the internetwork address ([network number]:node address) of the database machine. See the discussion on "Communication Between Systems" in the topic LMU/2 Needs and Functions for an explanation of which systems can communicate with each other. If destination is not used, the output is directed to the computer identified as MANAGING_SYSTEM_WITH_DATABASE in the managed system's LMU.INI file; if destination is used, it overrides the specification in the LMU.INI file. The data sent includes hardware, logical drives, user-defined data (from the USERVPD.DAT file), information about the files specified in the CRITFILE.DEF file and SYSLEVEL.xxx files. o The -s option is used only with the +r option; it suppresses the search for SYSLEVEL information, reducing the processing time for QUERYVPD and eliminating SYSLEVEL information from the data sent to the managing system with database. QUERYVPD +r -s QUERYVPD +rRTSRV101 -s o The +o option redirects the formatted output to a file. The default filename is QUERYVPD.DAT in the current directory on the managed computer. o The +p option causes the display of output to pause after each screenful of data. o The +q option suppresses the display of copyright information. o The +wpath option specifies a location to search for the user-defined data files (USERVPD.DAT, ADAPTERS.DEF, CRITFILES.DEF). The location specified becomes the first place searched for these files. In the QUERYVPD parameters, a plus sign (+) and slash (/) are equivalent; a minus sign (-) and a tilde (~) are equivalent. Any +option can be specified as /option, and any -option can be specified as ~option. The r option, for example, can be specified as either +r or /r; the s option can be specified as either -s or ~s. The slash (/), plus sign (+), minus sign (-), and tilde (~) are processed left to right as they appear in the command. Of contradictory options, such as +s and -s, or -s and +r, the rightmost option prevails. As a general rule, any plus options should be specified first, followed by any minus options. Examples: QUERYVPD (no options) displays the following kinds of information: o Hardware o Operating system o Logical drives o User data (from the USERVPD.DAT file) o Critical file information (on files identified in the CRITFILE.DEF file) QUERYVPD /r directs the following kinds of information to the LMU/2 database: o Hardware o Operating system o Logical drives o USERVPD.DAT data o CRITFILE.DEF files data o SYSLEVEL data (including current and previous corrective service diskette levels) Note that only Micro Channel adapters are recognized by QUERYVPD. ΓòÉΓòÉΓòÉ 8.1.2. LMUGETCF ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUGETCF ΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /RdbmachineΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Nnodename ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Ppath ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /K ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Aconfig ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Help information /Rdbmachine Remote Managing System. Default is LMU/2 Managing System with Database from LMU.INI. /Nnodename Node name for output files. Default is COMPUTERNAME from IBMLAN.INI. /Ppath Path for output files. Default is root directory of the boot drive. /K Keep output files. Default is erase. /Aconfig Configuration file name. Default is current default configuration file. LMUGETCF Command Line Help Information The LMUGETCF program collects information from the OS/2 EE or ES Communications Manager files in the workstation in which it runs, and directs the output to a managing system for use by a configuration data manager. The output data is in binary. The LMUGETCF program is executed remotely. Parameters: o The /rdbmachine option specifies the IBM managing system to which to send the output configuration information. The default managing system is the managing system with database specified in the workstation's IBMLAN.INI file. o The /nnodename option identifies the workstation and is used as the filename for the output file. If LMUGETCF is successful, the filename of the file containing the configuration information is nodename.IMP. If an error is encountered, the resulting file is left on the workstation and is named nodename.ERR. If this parameter is not specified, the COMPUTERNAME from the workstation's IBMLAN.INI file is used. o The /ppath option specifies the location of work space on the workstation disk to write a temporary file; it also specifies where to place the nodename.ERR if an error occurs. o The /k option directs that a copy of the output file (nodename.IMP) is to be left on the workstation in addition to transferring the file to a managing system. o The /aconfig option specifies the name of the Communications Manager configuration file from which to extract data. The default is the default configuration file used by the Configuration Manager in the workstation. ΓòÉΓòÉΓòÉ 8.2. Performance Data ΓòÉΓòÉΓòÉ Using PERFCAP provides centralization and collection of workstation performance across multiple machines in the network. Using PERFWACH, OSRWATCH, SRVWATCH, IPXWATCH, and event monitoring (also called thresholding) of workstation performance in order to generate generic alerts or event logging. Using APPWATCH provides monitoring of application programs in a workstation in order to generate generic alerts or event logging. ΓòÉΓòÉΓòÉ 8.2.1. PERFCAP ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇ PERFCAP ΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇdriveΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇpathΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇ /i<sec> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /f<min> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /d<min> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /m<cplrs> ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /x ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /r<rcvr> ΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇ /w<spec> ΓöÇΓöÇΓöÇΓöÇΓöÿ Option descriptions on next page. Press ENTER to continue. Options Default Description /f<min> 10 frequency (in minutes) of snapshot. /i<sec> 20 interval (in seconds) of snapshot. /d<min> 0 duration (in minutes) of snapshot period. /m<cplrs> (all) mask of data collection choices (see below). /x (noexit) SPMDCF exits completely if /x specified. /r<rcvr> (managn) data forwarded to a specific computer. /w<spec> STDOUT additionally write trace/debug info to a file. PERFCAP invokes SPMDCF every /f minutes for a length of /i seconds. At the end of an interval period, the aggregated data is sent to the managing system (the receiver can be overridden by the /r option). This process is repeated for /d minutes. When PERFCAP exits, SPMDCF remains quiesced unless /x was specified. The data collection mask (/m option) determines which performance data is collected. If specified, the input value should be one or more of the following: c (CPU data), p (Physical disk data), l (Logical disk data), r (RAM data), and s (Swap data). The default is to collect ALL data. PERFCAP Command Line Help Information PERFCAP directs the IBM System Performance Monitor/2 (SPM/2) in an individual OS/2 workstation to collect resource performance data in memory over interval periods of time. PERFCAP then forwards the data to a managing system with database for inclusion in the LMU/2 database. The data concerns the performance of resources in the workstation. The resources monitored are: o Processor utilization o Workstation memory o Physical disk activity o Swap activity o Logical I/O (reads, writes, opens, and closes). Note that any or all of these data types can be selected for collection (see the /m option described below). PERFCAP may be initiated through the command line interface of the workstation, or through the LMUCMD command from an administrator workstation. The PERFCAP command line interface parameters specify the timing intervals and optional actions. Note that the < and > in the help information indicate user-supplied data and are not entered as part of the parameter. o /isec - controls the capture interval in seconds. The default is 20 seconds. o /fmin - controls the capture frequency in minutes. The default is 10 minutes. o /dmin - controls the duration of PERFCAP execution in minutes. Any value greater than 1440 implies continuous execution. The default is one execution only. o /mcplrs - provides a mask to allow the user to select the type of data to be collected. One or more of the letters listed should be specified. Each letter corresponds to a data type as follows: c - Processor utilization (CPU data) p - Physical disk data l - Logical disk data r - Workstation memory (RAM data) s - Swap data Example: /mcpr specifies that processor utilization, physical disk, and workstation memory data are to be collected. The default is to collect ALL data. o /x - terminates the System Performance Monitor Data Collection Facility (SPMDCF) module when PERFCAP has completed the duration. If /x is not specified, the default is to leave SPMDCF resident in the system without collecting data (in a quiesced state). In this state, SPMDCF does not impact the workstation (with the exception of the memory it occupies). If the /x option is specified, SPMDCF is terminated at the same time that PERFCAP terminates. Between SPM/2 and LMU/2, several applications use the SPMDCF pipes (SPMMON, SPMLOG, PERFCAP, and PERFWACH). Since SPMDCF does not impact the system when an application is not using it, it is recommended that SPMDCF be left resident. This reduces the overhead of loading SPMDCF when an application requires it. o /rrcvr - directs the collected performance data to a different database machine than the one identified in the LMU.INI file in the workstation. The default is to send the collected data to the database machine specified by the MANAGING_SYSTEM_WITH_DATABASE key in the workstation LMU.INI file. o /wspec - writes trace and debug information to the standard output device or to the file named by spec, in addition to sending the collected data to the LMU/2 database. The default, if /w is specified and a file is not named, is to write to the standard output device. For example, PERFCAP /i30 /f5 /d60 /w tells PERFCAP to capture data for a 30-second interval, do this every 5 minutes for a full hour, leave SPMDCF resident when PERFCAP terminates, and write debug and summary data to the standard output device as PERFCAP executes. When PERFCAP gets control, it parses the input values and then attempts to open the SPMDCF system pipe. Three attempts are made to open this pipe with a 10-second wait between the attempts. If the system pipe is successfully opened, PERFCAP continues with the data collection. Otherwise, a request is initiated to start SPMDCF. Again, three attempts are made to open the system pipe. If the system pipe cannot be opened, PERFCAP determines the time for the next interval and sleeps until that time has expired. PERFCAP continues to loop for the entire duration, attempting three times on each pass to open the system pipe. When the system pipe is open, data collection takes place. Data collection proceeds by sending system pipe commands to start the SPM/2 memory analyzer (THESEUS), and to start full data collection. If an error is received during this exchange, PERFCAP bypasses the collection for that interval, determines the next frequency interval, and sleeps until that time is reached. Otherwise, the trace pipe is opened and trace data is received. Refer to System Performance Monitor/2 Reference Manual for details about the SPM/2 API and the trace record formats. PERFCAP reads buffers of trace data over the trace pipe and aggregates that data into tables kept in memory. This continues for the duration of the interval. At the end of the interval, PERFCAP appends a header to the data aggregates and sends them on the LMU/2 transport to the managing (database) system. At the database system, Database Manager tables are created or appended to include the data from that managed system. See LAN Management Utilities/2 Database Tables for the data that is collected. Once PERFCAP has sent off the data, it checks the duration value. If the duration is complete, PERFCAP checks whether SPMDCF should be terminated and takes the appropriate action. If the duration is not complete, PERFCAP checks the frequency period. If it is time to start another interval, SPMDCF is driven to begin data collection again. Otherwise, PERFCAP determines how long before the frequency time expires and sleeps for that time period. ΓòÉΓòÉΓòÉ 8.2.1.1. Operational Notes ΓòÉΓòÉΓòÉ 1. PERFCAP must be executed on a workstation that has SPM/2 installed. The information is probably more useful if the workstation for data collection is a server, but this is not a restriction. The data can be collected on any workstation. 2. PERFCAP cannot be used simultaneously with another SPM/2 application that uses the SPM API, such as PERFWACH, SPMMON, or SPMLOG. This is because the SPMDCF pipes may be used by only one application at a time. However, PERFCAP and PERFWACH can interleave their use of the system pipe so that one extracts trace data while the other sleeps. PERFCAP makes three attempts per frequency interval to open the system pipe. If the system pipe cannot be obtained, PERFCAP bypasses the data collection for that interval and sleeps for the remainder of the frequency period. Errors are not generated for situations where SPMDCF is not available and the applications continue trying to collect data for the complete duration. ΓòÉΓòÉΓòÉ 8.2.1.2. Watch Log for PERFCAP ΓòÉΓòÉΓòÉ If PERFCAP is invoked with the /w option, it writes tracking information to the standard output device or the specified file along with a data summary. The output that is produced is known as a watch log. Note that this information is produced in addition to sending data to the database machine. A PERFCAP watch log is included in Sample Logs because it reveals the manner in which PERFCAP operates. It is also useful in discussing the data produced from SPMDCF. ΓòÉΓòÉΓòÉ 8.2.2. PERFWACH ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇ PERFWACH ΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇΓöÇdriveΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇpathΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇ /i<sec> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /f<min> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /d<min> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /m<cplrs> ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /x ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /w<spec> ΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@proc ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@disk ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@swap ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@free ΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇ /@tcpu ΓöÇΓöÇΓöÇΓöÿ Option descriptions on next page. Press ENTER to continue. Options Default Description /f<min> 10 frequency (in minutes) of snapshot. /i<sec> 20 interval (in seconds) of snapshot. /d<min> 0 duration (in minutes) of snapshot period. /m<cplrs> (all) mask of data collection choices (see below). /x (noexit) SPMDCF exits completely if /x specified. /w<spec> STDOUT additionally write trace/alert info to a file. /@proc 0 create alert for a process that exceeds p%. /@disk 0 create alert if disk activity exceeds p%. /@swap 0 create alert if swap activity exceeds p%. /@free 0 create alert if free memory falls below p%. /@tcpu 0 create alert if total cpu utilization exceeds p%. NOTE: threshold specification of 0 indicates 'do not monitor'. PERFWACH invokes SPMDCF every /f minutes for a length of /i seconds. At the end of an interval period, the aggregated data is analyzed for exceptions (based on the /@ threshold specifications). A threshold exception causes a generic alert to be sent to the Fault Manager. The data collection mask (/m option) determines which performance data is collected. If specified, the input value should be one or more of the following: c (CPU data), p (Physical disk data), l (Logical disk data), r (RAM data), and s (Swap data). The default is to collect ALL data. PERFWACH Command Line Help Information Like PERFCAP, PERFWACH operates over the time intervals specified on the command line, driving SPMDCF to collect workstation performance data in memory. The difference is that PERFWACH does not send data to the LMU/2 database. Instead, PERFWACH monitors the data aggregated in memory and, if it finds indications that a designated threshold has been exceeded, PERFWACH sends a generic alert to the fault management system. The PERFWACH command line parameters specify the timing intervals and optional actions. Note that the < and > in the help information indicate user-supplied data and are not entered as part of the parameter. o /isec - controls the capture interval in seconds. The default is 20 seconds. o /fmin - controls the capture frequency in minutes. The default is 10 minutes. o /dmin - controls the duration of PERFCAP execution in minutes. Any value greater than 1440 implies continuous execution. The default is one time only. o /mcplrs - provides a mask to allow the user to select the type of data to be collected. One or more of the letters listed should be specified. Each letter corresponds to a data type as follows: c - Processor utilization (CPU data) p - Physical disk data l - Logical disk data r - Workstation memory (RAM data) s - Swap data Example: /mcpr specifies that processor utilization, physical disk, and workstation memory data are to be collected. The default is to collect ALL data. o /x - terminates the System Performance Monitor Data Collection Facility (SPMDCF) module when PERFCAP has completed the duration. The default is to leave SPMDCF resident. o /wspec - writes trace and alert information to the standard output device or to the file named by spec. The default, if /w is specified and a file is not named, is to write to the standard output device. In addition to the control values, PERFWACH accepts threshold specifications to determine the conditions and limits to be monitored. o /@PROCp - indicates that PERFWACH should monitor process activity and generate a generic alert if the execution time of a process exceeds p% of the time available to all processes during the capture interval. p is a percentage value between 0 and 100; the default is 0 and indicates "do not monitor". The alert generated is LMU5101I. o /@DISKp - indicates that PERFWACH should monitor disk activity and generate a generic alert if the execution time for disk activity exceeds p% of the capture interval. p is a percentage value between 0 and 100; the default is 0 and indicates "do not monitor". The alert generated is LMU5102I. o /@SWAPp - indicates that PERFWACH should monitor swap activity and generate a generic alert if the execution time for swap activity exceeds p% of the capture interval. p is a percentage value between 0 and 100; the default is 0 and indicates "do not monitor". The alert generated is LMU5103I. o /@FREEp - indicates that PERFWACH should monitor free memory availability and generate a generic alert if the free memory in the workstation falls below p% of the total memory available for swapping. p is a percentage value between 0 and 100; the default is 0 and indicates "do not monitor". The alert generated is LMU5104I. o /@TCPUp - indicates that PERFWACH should monitor total central processing unit (CPU) utilization and generate a generic alert if the CPU utilization in the workstation exceeds p% of the possible CPU utilization. p is a percentage value between 0 and 100; the default is 0 and indicates "do not monitor". The alert generated is LMU5105I. These thresholds can also be established in the LMU.INI file. PERFWACH reads the control file profile values listed below: PERFWACH_PROC corresponds to /@PROC PERFWACH_DISK corresponds to /@DISK PERFWACH_SWAP corresponds to /@SWAP PERFWACH_FREE corresponds to /@FREE PERFWACH_TCPU corresponds to /@TCPU PERFWACH first extracts .INI file values for the above items (if they are present). If a profile entry is not present, the default ("do not monitor") is assumed. Next, PERFWACH applies command line thresholds as specified. A threshold specified from the command line overrides any value that may have previously been established. For example, a workstation has the following .INI values defined: PERFWACH_PROC set to 80 PERFWACH_DISK set to 10 PERFWACH_FREE set to 5 and the user enters the following command line: perfwach /i60 /f10 /d60 /@proc90 /@disk0 The following thresholds would be in use for this instance of PERFWACH. Threshold values: PROC:90 DISK:00 SWAP:00 FREE:05 TCPU:00 SWAP and TCPU were not specified anywhere and default to 0. PROC was overridden at the command line to 90. DISK was turned off at the command line, setting the threshold to 0. FREE was not specified at the command line and so the .INI value is used. ΓòÉΓòÉΓòÉ 8.2.2.1. Operational Notes ΓòÉΓòÉΓòÉ 1. PERFWACH must be executed on an OS/2 workstation that has SPM/2 installed. The information is probably more useful if the workstation for data collection is a server, but this is not a restriction. The data can be collected on any workstation. 2. The SPMDCF system pipe can be used by only one application at a time. This means that PERFWACH cannot execute simultaneously with another application that uses the SPM API (such as PERFCAP, SPMMON or SPMLOG). However, PERFCAP and PERFWACH can interleave their use of the system pipe so that one extracts trace data while the other sleeps. PERFWACH makes three attempts per frequency interval to open the system pipe. If the system pipe cannot be obtained, PERFWACH bypasses the data collection for that interval and sleeps for the remainder of the frequency period. Errors are not generated for situations where SPMDCF is not available and the applications continue trying to collect data for the complete duration. ΓòÉΓòÉΓòÉ 8.2.2.2. Watch Log for PERFWACH ΓòÉΓòÉΓòÉ If PERFWACH is invoked with the /w option, it writes tracking information to the standard output device or a specified file, along with some data summarization. The output that is produced from the /w option is referred to as a watch log. Note that this information is produced in addition to any alerts that may be generated. A PERFWACH watch log is included in Sample Logs because it reveals the manner in which PERFWACH operates. ΓòÉΓòÉΓòÉ 8.2.3. OSRWATCH ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇ OSRWATCH ΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇΓöÇdriveΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇpathΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇ /s<server> ΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /f<min> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /d<min> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /w<spec> ΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /a<0|1> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@ncbs ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@nses ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@nerr<n> ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@nabt<n> ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@ndti<n> ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@ndt1<n> ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@ndto<n> ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /@nbfx<n> ΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇ /@nlgn<n> ΓöÇΓöÇΓöÇΓöÿ Option descriptions on next page. Press ENTER to continue. Options Default Description /s<server> local domain controller name of the adapter set. /f<min> 10 frequency (in minutes) of snapshot. /d<min> 0 duration (in minutes) of snapshot period. /w<spec> STDOUT additionally write trace/alert info to a file. /a<0|1> 0 specify adapter as primary (0) or secondary (1). /@ncbs 0 alert if NCBs fall below percentage p%. /@nses 0 alert if NETBIOS sessions fall below percentage p%. /@nerr<n> 0 alert if transmission errors are >= count n. /@nabt<n> 0 alert if aborted transmissions are >= count n. /@ndti<n> 0 alert if DLC Ti (inactivity) timeouts are >= count n. /@ndt1<n> 0 alert if DLC T1 (response) timeouts are >= count n. /@ndto<n> 0 alert if DLC Ti or T1 timeouts are >= count n. /@nbfx<n> 0 alert if buffers are exhausted >= count n. /@nlgn<n> 0 alert if number of users logged on >= count n. NOTE: threshold specification of 0 indicates 'do not monitor'. OSRWATCH Help Information OSRWATCH collects status from a known set of adapters, using the IBM LAN Requester NetLogonEnum API as the method to obtain the set of IBM NETBIOS names to query. The only workstations that are queried are those that are logged on to a particular IBM LAN server. OSRWATCH accepts the following input parameters. Note that the < and > in the help information indicate user-supplied data and are not entered as part of the parameter. o /sserver - the computer name of the domain controller of the set of IBM LAN requesters that are to be monitored. The default for this parameter is the primary domain controller of the workstation on which OSRWATCH is executing. o /fmin - the frequency interval in minutes for collecting adapter status. o /dmin - the duration in minutes to maintain the collection. Any value greater than 1440 implies continuous operation. o /wspec - write trace and alert information to the standard output device or to the file named. The default, if /w is specified and a file is not named, is to write to the standard output device. o /@NCBSp - monitor the Number of Control BlockS. If the number of available NETBIOS Control Blocks (NCBs) to defined maximum NCBs is below the percentage specified, generate a generic alert. p is a percentage value between 0 and 100; the default is 0 and indicates "do not monitor". The alert generated is LMU5201I. o /@NSESp - monitor the Number of SESsions. If the number of available NETBIOS sessions to the defined maximum number of sessions is below the percentage specified, generate a generic alert. p is a percentage value between 0 and 100; the default is 0 and indicates "do not monitor". The alert generated is LMU5202I. o /@NERRn - monitor the Number of packet ERRors at each adapter. If the number of packet errors (transmit and receive) in a collection interval is greater than or equal to the specified value, generate a generic alert. n is a number between 0 and 32767; the default is 0 and indicates "do not monitor". The alert generated is LMU5203I. o /@NABTn - monitor the Number of ABorTed transmissions at each adapter. If the number of aborted transmissions in a collection interval is greater than or equal to the specified value, generate a generic alert. n is a number between 0 and 32767; the default is 0 and indicates "do not monitor". The alert generated is LMU5204I. o /@NDTIn - monitor the Number of inactivity timer (Ti) timeouts at each adapter. If the number of Data Link Control (DLC) Ti timeouts detected during the collection interval is greater than or equal to the specified value, generate a generic alert. n is a number between 0 and 32767; the default is 0 and indicates "do not monitor". The alert generated is LMU5208I. o /@NDT1n - monitor the Number of response timer (T1) timeouts at each adapter. If the number of Data Link Control (DLC) T1 timeouts detected during the collection interval is greater than or equal to the specified value, generate a generic alert. n is a number between 0 and 32767; the default is 0 and indicates "do not monitor". The alert generated is LMU5209I . o /@NDTOn - monitor the Number of TimeOuts at each adapter. If the number of Data Link Control (DLC) timeouts (T1 or Ti) detected during the collection interval is greater than or equal to the specified value, generate a generic alert. n is a number between 0 and 32767; the default is 0 and indicates "do not monitor". The alert generated is LMU5205I. o /@NBFXn - monitor the Number of BuFfers eXhausted at each adapter. If the count of buffers (adapter request and transmit) not available in a collection interval is greater than or equal to the number specified, generate a generic alert. n is a number between 0 and 32767; the default is 0 and indicates "do not monitor". The alert generated is LMU5207I. o /@NLGNn - monitor the Number of users LoGged oN. If the number of active requesters in the domain is greater than or equal to the number specified, generate a generic alert. n is a number between 0 and 32767; the default is 0 and indicates "do not monitor". The alert generated is LMU5206I. OSRWATCH uses the provided IBM LAN server name to determine the set of workstations (adapters) to monitor. The IBM LAN server is queried to establish a list of IBM LAN requesters logged on to that server. This list determines the set of adapters that are monitored. OSRWATCH uses the /f and /d parameters to determine the total number of loops to perform (note that execution can be forced to be continuous). On each loop, OSRWATCH establishes the list of adapters to query and then queries each one individually. The returned data for each adapter is matched to existing (previous) data based on the requester ID. Once the data is collected, each set of workstation data is analyzed for a change in conditions. Where thresholds are specified, the change in condition can result in a generic alert if that condition equals or exceeds the threshold value. If a threshold is equalled or exceeded and an alert is generated, the next loop and data collection may or may not cause another alert to be generated. If there is no change in condition, no alert will be generated. If there is a condition change and the threshold continues to be equalled or exceeded, a new alert is generated. For example, the user issues the following command: osrwatch /f3 /d60 /w /@ncbs10 meaning: monitor the adapters in my domain every 3 minutes for an hour, and write the output to STDOUT. If any workstation adapter shows an available NCB count of less than 10%, generate an alert. Assume that a workstation in the domain has a defined maximum of 30 NCBs and the current number of unused NCBs is 3: 1. At time0, the data for that workstation is extracted and the NCB count does not exceed the threshold. No alert is generated. 2. At time1, the NCB count falls to 1. Now the available NCB count is below 10% and an alert is generated. 3. At time2, the NCB count is still 1. Because no condition changed between this collection and the previous one, no alert is generated. 4. At time3, the NCB count is still 1. Again, no alert is generated. 5. At time4, the NCB count is 2. This represents a change in condition and the NCB count remains below 10%, so an alert is generated. 6. At time5, the NCB count comes back to 3. This represents a change in condition, but now the threshold is not exceeded. No alert is generated. The user data for each generated alert identifies the threshold option. In addition, this user data string is placed in the LMU/2 messages log file of the workstation that executes OSRWATCH. As with PERFWACH, the thresholds can also be established in the LMU.INI file. OSRWATCH reads the profile values listed below: OSRWATCH_NCBS corresponds to /@NCBS OSRWATCH_NSES corresponds to /@NSES OSRWATCH_NERR corresponds to /@NERR OSRWATCH_NABT corresponds to /@NABT OSRWATCH_NDTO corresponds to /@NDTO OSRWATCH_NBFX corresponds to /@NBFX OSRWATCH_NLGN corresponds to /@NLGN OSRWATCH_NDTI corresponds to /@NDTI OSRWATCH_NDT1 corresponds to /@NDT1 The values in the LMU.INI file are used first but can be overridden by specifying values on the OSRWATCH command line. ΓòÉΓòÉΓòÉ 8.2.3.1. Operational Notes ΓòÉΓòÉΓòÉ OSRWATCH operates from any OS/2 workstation on the ring and gathers data from all adapters on the ring without requiring code to execute at each workstation. Part of the data that is returned includes the level of NETBIOS in the adapter. Since DOS clients run a different level of NETBIOS than OS/2 clients, the DOS clients can be differentiated from OS/2 clients in the data collection. DOS client activity on the ring can be monitored without executing code in those clients. ΓòÉΓòÉΓòÉ 8.2.3.2. Watch Log for OSRWATCH ΓòÉΓòÉΓòÉ In addition to generating alerts, OSRWATCH can be set to create a log of activity (/w option) that is seen across the adapter status that is collected. An example OSRWATCH watch log is included in Sample Logs. ΓòÉΓòÉΓòÉ 8.2.4. SRVWATCH ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇ SRVWATCH ΓöÇΓöÇΓöÇΓöÇ> ΓööΓöÇΓöÇdriveΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇpathΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö┤ΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇ /s<server> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /f<min> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /d<min> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /w<spec> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /t ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /@savr<ms> ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γöñ Γöé Γöö <,cnt> ΓöÇΓöÿΓöé Γö£ΓöÇΓöÇ /@srbf<n> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /@sbbf<n> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /@tses<n> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /@tcon<n> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /@topn<n> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /@sses<n> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /@scon<n> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ /@sopn<n> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇ /@sidl<min> ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Option descriptions on next page. Press ENTER to continue. Options Default Description /s<server> local name of server to monitor. /f<min> 3 frequency (in minutes) of statistics collection. /d<min> 0 duration (in minutes) of statistics collection. /w<spec> STDOUT additionally write watch/alert info to a file. /t display session detail per user. /@savr<ms><,cnt> 0,5 bump exception count if server average response time exceeds <ms>. Create an alert after <cnt> exceptions. /@srbf<n> 0 alert if regular buffer allocation failures are >= n. /@sbbf<n> 0 alert if big buffer allocation failures are >= n. /@tses<n> 0 alert if the number of sessions at this server are >= n. /@tcon<n> 0 alert if the number of connections at this server are >= n. /@topn<n> 0 alert if the number of file opens at this server are >= n. /@sses<n> 0 alert if the number of sessions for a single user are >= n. /@scon<n> 0 alert if the number of connections for a single user are >= n. /@sopn<n> 0 alert if the number of file opens for a single user are >= n. /@sidl<min> 0 alert if the session idle time for a single user is >= min. NOTE: threshold specification of 0 indicates 'do not monitor'. SRVWATCH Help Information Run SRVWATCH from: o A workstation with ADMIN authority to the IBM LAN server that is to be monitored o An IBM LAN server to be monitored. SRVWATCH collects statistics information from an IBM LAN Server using the NetStatisticsGet2 API. As with OSRWATCH, the data is collected on an interval basis and monitored for exceptions to user-specified thresholds. SRVWATCH accepts the following input parameters. Note that the < and > in the help information indicate user-supplied data and are not entered as part of the parameter. o /sserver - the computer name of the IBM LAN server from which to gather and monitor statistics. This name must be the requester ID (identified by COMPUTERNAME in the IBMLAN.INI file in the server). The default for this parameter is the server to which this workstation is logged on. o /fmin - the frequency interval in minutes for collecting server statistics. o /dmin - the duration in minutes to maintain the statistics collection. Any value greater than 1440 implies continuous operation. o /wspec - write monitored information to the standard output device or to the file named. o /@savrms[,cnt] - monitor the Server AVerage Response time. - ms - response time threshold, in milliseconds. If the average response time exceeds the millisecond value specified for the threshold, generate a generic alert. ms is a number between 0 and 60000, inclusive. - cnt - optional count of consecutive excesses before generating an alert. For example, /@savr100,4 specifies: "generate an alert if the server average response time exceeds 100 ms in four consecutive collection intervals." The alert generated is LMU5310I. o /@srbfn - monitor the Server Request BuFfer allocation failures, and generate a generic alert if the statistics indicate a number of request buffer allocation failures that equals or exceeds the threshold n. n is a number between 0 and 60000. Note that the OS/2 LAN Server parameter numreqbuf controls the number of request buffers available at the server. If this alert is generated, numreqbuf may need to be tuned. (See IBM Operating System/2 Local Area Network Server Version 1.3 Network Administrator's Guide for information on tuning the parameter.) The alert generated is LMU5311I. o /@sbbfn - monitor the Server Big BuFfer allocation failures, and generate a generic alert if the statistics indicate a number of big buffer allocation failures that equals or exceeds the threshold n. n is a number between 0 and 60000. Note that the OS/2 LAN Server parameter numbigbuf controls the number of big buffers available at the server. If this alert is generated, numbigbuf may need to be tuned. (See IBM Operating System/2 Local Area Network Server Version 1.3 Network Administrator's Guide for information on tuning the parameter.) The alert generated is LMU5312I. o /@tsesn - monitor the total sessions at the server, and generate a generic alert if the statistics indicate a number of sessions that equals or exceeds the threshold n. n is a number between 0 and 60000. The alert generated is LMU5313I. o /@tconn - monitor the total connections at the server (NET USE is a connection), and generate a generic alert if the statistics indicate a number of connections that equals or exceeds the threshold n. n is a number between 0 and 60000. The alert generated is LMU5314I. o /@topnn - monitor the total file opens at the server, and generate a generic alert if the statistics indicate a number of file opens that equals or exceeds the threshold n. n is a number between 0 and 60000. The alert generated is LMU5315I. o /@ssesn - monitor the individual user sessions at the server, and generate a generic alert if the statistics indicate a number of sessions from a single requester that equals or exceeds the threshold n. n is a number between 0 and 60000. The alert generated is LMU5316I. o /@sconn - monitor the individual user connections at the server, and generate a generic alert if the statistics indicate a number of connections with a single requester that equals or exceeds the threshold n. n is a number between 0 and 60000. The alert generated is LMU5317I. o /@sopnn - monitor the individual user file opens at the server, and generate a generic alert if the statistics indicate a number of user file opens from a single requester that equals or exceeds the threshold n. n is a number between 0 and 60000. The alert generated is LMU5318I. o /@sidln - monitor the individual session idle time at the server, and generate a generic alert if the statistics indicate an amount of idle time for sessions from a single requester that equals or exceeds the threshold n. n is a number between 0 and 60000, and represents minutes of idle time. Note that, although this threshold is expressed in minutes, the amount of idle time in the SRVWATCH watch log is expressed in seconds. The alert generated is LMU5319I. Based on the frequency and duration specifications, SRVWATCH collects statistical information from the indicated server. On each pass, the data is analyzed for exceptions to the threshold specifications. If a threshold is equalled or exceeded, an alert is generated and forwarded to the fault manager. The very first collection of data from the server is not part of the monitored data and cannot cause an alert to be generated. If a watch log is requested (/w option), the information monitored for thresholds is printed. Information written to the watch log includes: o The server average response time, timestamped o Request buffer allocation failures and big buffer allocation failures o Any alerts that are generated. Note that every time the statistics are collected, the counters maintained in the server are reset to 0. This means that the frequency specification (/f parameter) provides the time factor in interpreting the data. For example, the user issues the following command: srvwatch /f3 /d60 /w /@savr500,5 /@sbbf5 /@srbf5 and receives the following watch log entries: 08/13/1991 08:34:16 Response time: 713 ms - Big buffer fail: 81 08/13/1991 08:37:16 Response time: 28 ms 08/13/1991 08:40:16 Response time: 160 ms 08/13/1991 08:43:16 Response time: 94 ms - Big buffer fail: 4 08/13/1991 08:46:16 Response time: 67 ms The first collection represents the statistics counters since they were last reset, and is not used in determining threshold exceptions. Once reset, the values represent changes over 3-minute intervals. At 08:37, the average response time over the last 3 minutes was 28 ms. In the next 3 minutes, the average response time jumped to 160 ms. At 08:43, four big buffer allocation failures were found. As with other performance applications that accept threshold specifications, the thresholds may also be established in the LMU.INI file. SRVWATCH reads the control file profile values for the keys listed below: SRVWATCH_SAVR corresponds to /@SAVR SRVWATCH_SRBF corresponds to /@SRBF SRVWATCH_SBBF corresponds to /@SBBF SRVWATCH_TSES corresponds to /@TSES SRVWATCH_TCON corresponds to /@TCON SRVWATCH_TOPN corresponds to /@TOPN SRVWATCH_SSES corresponds to /@SSES SRVWATCH_SCON corresponds to /@SCON SRVWATCH_SOPN corresponds to /@SOPN SRVWATCH_SIDL corresponds to /@SIDL The SRVWATCH_SAVR value specification is identical to that for the /@SAVR option (ms[,cnt]), that is, number of milliseconds with an optional count value separated by a comma. The .INI file values are used first, if found, and can be overridden by specifying threshold options on the SRVWATCH command line. ΓòÉΓòÉΓòÉ 8.2.4.1. Operational Notes ΓòÉΓòÉΓòÉ SRVWATCH can be run from any workstation with ADMIN authority to the server to be monitored, but remember that each statistics collection at the server resets the counters to 0. If SRVWATCH is run from more than one workstation against the same server at the same time, then the counters at that server are independently reset by each SRVWATCH instance. Consequently, the data cannot be interpreted as statistics over a known time interval. ΓòÉΓòÉΓòÉ 8.2.4.2. Watch Log for SRVWATCH ΓòÉΓòÉΓòÉ In addition to generating alerts, SRVWATCH can be set to create a log (/w option) of response-time and buffer events in the server. ΓòÉΓòÉΓòÉ 8.2.5. APPWATCH ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ APPWATCH ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Iiterations ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Ssleep ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Ttable ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Help information /Iiterations Process (PSTAT) scanning iterations; range is 0 to 65535 (use 0 to loop forever); default is 1 /Ssleep Sleep interval (in minutes) between iterations; range is 1 to 1440 minutes; default is 5 minutes /Ttable Fully qualified file name of table containing list of critical applications; default is value specified for APPWATCH_TABLE key in LMU.INI APPWATCH Help Information APPWATCH runs in an OS/2 workstation, and uses the OS/2 PSTAT command to determine whether the applications listed in the APPWATCH table are loaded in memory in the workstation. If APPWATCH cannot find an application, or finds fewer or more instances of the application than specified in the table, APPWATCH can generate an alert. Parameters: o /iiterations - The number of times to check for applications. The range is 0 to 65535. The default is 1 time. Use 0 to check endlessly. o /ssleep - the time in minutes between each query. The range is 1 to 1440 minutes. The default is 5 minutes. o /ttable - The drive, path, and filename of the table that contains the list of applications to monitor. If this parameter is not specified, the default is the table specified for the APPWATCH_TABLE key in the LMU.INI file. The table format is described in APPWATCH File Table. ΓòÉΓòÉΓòÉ 8.2.6. IPXWATCH ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ IPXWATCH ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Iiterations ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Ssleep ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@CFRFthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@CIPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@CMPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@COSFthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@CRPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@CSPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@DFRFthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@DIPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@DMPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@DOSFthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@DRPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@DSPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Help information /Iiterations Statistics collection iterations; range is 0 to 65535 (use 0 to loop forever); default is 1 /Ssleep Sleep interval (in minutes) between iterations; range is 1 to 1440; default is 5 minutes /@CFRFthreshold Cumulative Find Route Failures /@CIPCthreshold Cumulative Ignore received Packet Count /@CMPCthreshold Cumulative Malformed Packet Count /@COSFthreshold Cumulative Open Socket Failures /@CRPCthreshold Cumulative Receive Packet Count /@CSPCthreshold Cumulative Send Packet Count /@DFRFthreshold Delta Find Route Failures /@DIPCthreshold Delta Ignore receive Packet Count /@DMPCthreshold Delta Malformed Packet Count /@DOSFthreshold Delta Open Socket Failures /@DRPCthreshold Delta Receive Packet Count /@DSPCthreshold Delta Send Packet Count Range of threshold values is 1 to 2147483647; default is "do not check" IPXWATCH Help Information IPXWATCH runs in an OS/2 workstation that is running the Novell NetWare Requester for OS/2. The IBM OS/2 LAN Requester can also be present, but the Novell Requester for OS/2 must be present. IPXWATCH monitors the statistics for the Internetwork Packet Exchange (IPX) protocol in the workstation in which it is running, and generates a generic alert whenever a specified threshold is exceeded. In the IPXWATCH help, the term "cumulative" refers to "since the requester has been running"; the term "delta" refers to "since the last iteration". The delta threshold parameters apply only if the /i parameter specifies more than one collection, and otherwise are not checked. Parameters: o /iiterations - the number of times to collect the statistics and compare them to the threshold values. The range is 0 - 65535. The default is 1 time. Use 0 to collect statistics without limiting the number of collections. o /ssleep - the time in minutes between each collection. The range is 1 to 1440 minutes. The default is 5 minutes. o Thresholds - for each of the thresholds, generate a generic alert when the count for the event exceeds the threshold value you specify. The meaning of each of the thresholds is self-explanatory; see the Novell documentation on IPX statistics for details. ΓòÉΓòÉΓòÉ 8.3. Fault Management ΓòÉΓòÉΓòÉ Using LMU/2 fault management allows you to provide automated recovery for fault conditions at OS/2 managed stations, and to provide appropriate notification to IBM NetView or to IBM LAN Network Manager. ΓòÉΓòÉΓòÉ 8.3.1. At the Fault Reporter ΓòÉΓòÉΓòÉ The LMU/2 programs such as PERFWACH and OSRWATCH may generate generic alerts in the stations in which they execute. To enable these alerts to be forwarded to the fault manager, enter the following line command in the STARTUP.CMD file or in an OS/2 window at each managed, managing, and administrator workstation system. DETACH AUEPITCH Note: If running LMUCLI in the station, the DETACH AUEPITCH statement is not necessary; LMUCLI automatically detaches AUEPITCH. If you used LMUCUST in these stations, the statement may have been placed in the LMUSTART.CMD file in C:\LMU2 for you. To stop AUEPITCH (that is, to stop the forwarding of generic alerts to the fault manager), enter the following at the command line on the affected managed, managing, and administrator workstations, or as the command string in an LMUCMD command to the managed system: LMUQUERY /t AUEPITCH ΓòÉΓòÉΓòÉ 8.3.2. At the Fault Manager ΓòÉΓòÉΓòÉ To process generic alerts, start the AUERECVR and AUECATCH processes on the fault manager. AUERECVR reads and internally formats the alerts table file that you created to specify which generic alerts to process (see User-Defined Table for details on the alerts table). At the fault manager station, enter the following line commands in the STARTUP.CMD file or in an OS/2 window. START /C AUERECVR START /C AUECATCH n where n is a number that specifies where to forward generic alerts: 1 Forward generic alerts to IBM NetView 2 Forward generic alerts to LAN management functional address (IBM LAN Manager or IBM LAN Network Manager) 3 Do not forward generic alerts. If no parameter is specified, AUECATCH defaults to 1 (forward alerts to NetView). Note: If you used LMUCUST to customize the fault manager, the statements may have been placed in the LMUSTART.CMD file in C:\LMU2 for you. To stop the fault manager (that is, to stop AUECATCH, AUERECVR, or both, and thus to stop the processing of generic alerts), enter the following at the fault manager command line: LMUQUERY /t AUECATCH AUERECVR If the fault manager is also a managed system, the LMUQUERY command can be the command string in an LMUCMD command to the fault manager. ΓòÉΓòÉΓòÉ 8.3.3. AUEPITCH ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ AUEPITCH ΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ AUEPITCH syntax AUEPITCH has no parameters. Detach AUEPITCH to activate the fault reporter function in the station. If the station is a LAN server or requester, the server or requester function must be started and running before detaching AUEPITCH. ΓòÉΓòÉΓòÉ 8.3.4. AUECATCH ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ AUECATCH ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ 1 ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ drive ΓöÇΓöÿ ΓööΓöÇ path ΓöÇΓöÿ Γö£ΓöÇΓöÇ 2 ΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇ 3 ΓöÇΓöÇΓöñ ΓööΓöÇΓöÇ ? ΓöÇΓöÇΓöÿ Options: 1 : Route alerts to NetView session ( Comm. Mgr. ). ** 2 : Route alerts to LAN Network Manager ( IEEE 802.2 ). 3 : Do not route alerts. ? : This help panel. ** Default if no option entered is option 1. AUECATCH Help At a fault manager, start both AUERECVR and AUECATCH in order to process generic alerts. AUECATCH designates where to forward the alerts. Parameters: o 1 - forward the generic alerts to IBM NetView using an OS/2 Communications Manager session with NetView. This is the default. o 2 - forward the generic alerts to a LAN management functional address, such as the IBM LAN Manager or the IBM LAN Network Manager, using the IEEE 802.2 interface. You can specify the adapter address of a particular LAN management functional address in the FM_FORWARDING_ADDR parameter in the LMU.INI file in the station in which AUECATCH is running. o 3 - do not forward the generic alerts. o ? - produces the AUECATCH help panel. ΓòÉΓòÉΓòÉ 8.3.5. AUERECVR ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ AUERECVR ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ drive ΓöÇΓöÿ ΓööΓöÇ path ΓöÇΓöÿ Γö£ΓöÇΓöÇ C ΓöÇΓöÇΓöñ ΓööΓöÇΓöÇ ? ΓöÇΓöÇΓöÿ Options: C : Pass the computer name of the computer which originated the alert. ? : This help panel. AUERECVR Help At a fault manager, start both AUERECVR and AUECATCH in order to process generic alerts. AUERECVR processes the alerts against the user-created alerts table, initiating notifications or automation as specified in the table. Optionally, AUERECVR appends to the command string in a table entry the name of the computer that generated the alert, passing that name as part of the notification or automation process. Parameters: o c - append to the alert table entry command string the computer name of the computer generating the alert. o ? - produces the AUERECVR help panel. ΓòÉΓòÉΓòÉ 8.3.6. VIRALERT ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ VIRALRT ΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ VIRALERT Syntax VIRALERT is intended to be run following a virus-detection program in an OS/2 workstation. When executed, VIRALERT builds a generic "virus detected" alert and sends the alert to the fault manager specified in the LMU.INI file in the workstation on which it executes. Make certain the other fault reporter components are available to the workstation when using VIRALERT. AUEUSRGA must be in a directory pointed to by the LIBPATH of the system, and AUEPITCH must be running. VIRALERT does not itself detect the virus. It must be run only after a program is run that checks for the possible existence of a virus, and only if the program finds a potential virus. Its purpose is to alert the central site operator of the detected virus condition. It is the user's responsibility to set up the conditional logic to run VIRALERT. This can be done by using a REXX program or .CMD file to: 1. Run the virus-checking program of your choice 2. Check the return code from the virus-checking program for a "virus detected" condition (generally, any non-zero return code) 3. Run VIRALERT only if the virus-checking program produced a "virus detected" return code. ΓòÉΓòÉΓòÉ 8.3.7. Generic Alert Routing ΓòÉΓòÉΓòÉ When you start AUECATCH in the fault manager, you specify whether you want to forward generic alerts to NetView or to IBM LAN Network Manager. The following material discusses configuration-specific parameters to accomplish this routing in the fault manager. o Forwarding to NetView o Forwarding to LAN Network Manager Note: The generic alerts produced by the LMU/2 programs are identified in topic LMU/2 Generic Alerts. ΓòÉΓòÉΓòÉ 8.3.7.1. Forwarding to NetView ΓòÉΓòÉΓòÉ In order to forward generic alerts to NetView, you will need to create definitions in OS/2 Communications Manager that enable establishment of a system service control point-physical unit (SSCP-PU) session with your host VTAM*. Your VTAM System Programmer should be very familiar with the definitions required at the host to accomplish this. At the workstation, you may need to make updates to the following profiles and definitions: o SNA Feature Profile - SNA Base Profile (PU Name, Network Name, Node ID) Your Host VTAM System Programmer should supply the necessary values for these parameters. o LAN Feature Profiles - IEEE 802.2 Profile (Maximum Number of SAPs, Users, Link Stations) If you had no SNA presence in the workstation prior to installing LMU/2 fault manager, you will need to increment the Maximum Number of SAPs, Users, and Link Stations by 1. If you were running 3270 emulation or advanced program-to-program communications (APPC) applications prior to installing fault manager, it should not be necessary to modify the number of SAPs or Users, but an additional link station may be required if the SSCP-PU session end point (at the host) is unique for fault manager. - NETBIOS (Maximum Number of Link Stations) You should not need to modify any values in this profile. o 3270 Feature Profiles IBM Token-Ring Network 3270 Profile (Connection) Your host VTAM system programmer should supply the necessary values for this parameter. ΓòÉΓòÉΓòÉ 8.3.7.2. Forwarding to IBM LAN Network Manager ΓòÉΓòÉΓòÉ Generic alerts are forwarded to IBM LAN Network Manager using the IBM LAN Network Manager's Alert Transport Services. To use these services, the fault manager becomes an additional IEEE 802.2 application in your workstation; if you receive messages indicating insufficient resources in your workstation, you may need to make updates to the following profiles and definitions: o LAN Feature Profiles - IEEE 802.2 Profile (Maximum Number of SAPs, Maximum Number of Users) You may need to increment the Maximum Number of SAPs and the Maximum Number of Users by 1. - NETBIOS (Maximum Number of Link Stations) You should not need to modify any values in this profile. Notes: 1. For all levels of OS/2, the Maximum Number of SAPs must be equal to or greater than the Maximum Number of Users. 2. For OS/2 1.3, there is a limit on the number of Users that can use the Token-Ring Network adapter at the same time. The limit depends on the level of OS/2 1.3 and the Corrective Service Diskettes (CSDs) that have been applied. For example, the original version of OS/2 1.3 has a limit of five Users; later CSDs raised the limit to seven or greater. Examples of applications and services that are Users on the adapter are: SNA (SSCP-PU), LAN Requester, Alert Transport Services, and IBM LAN Network Manager; in the same workstation, this would be four Users of the Token-Ring Network adapter. ΓòÉΓòÉΓòÉ 8.3.8. User-Defined Table ΓòÉΓòÉΓòÉ The alerts table identifies which alerts the fault manager is to process, and what action to take for each alert. The file name and location of the alerts table must be specified in the LMU.INI profile in the fault manager computer. Entries in the table can specify forwarding an alert, or performing some other action, or both. If a generic alert has no match in the table, or the table does not exist or is unavailable, the fault manager forwards the alert. The alert destination (IBM NetView or IBM LAN Network Manager) is specified on the AUECATCH command. Using a text editor, create the alerts table file. Identify the expected alerts and the action you want taken. The format of the table is described in the topic Alerts Table Format Note: The generic alerts produced by the LMU/2 programs are identified in topic LMU/2 Generic Alerts. ΓòÉΓòÉΓòÉ 8.3.8.1. Alerts Table Format ΓòÉΓòÉΓòÉ The table contains a single line for each alert to be processed. Each field in the line must be present, must have no embedded blanks, and must be delimited by at least one blank. Each line consists of two main parts: KEY DATA The portion that identifies the alert to be processed. If the fault manager matches this data with that contained in a generic alert, the alert is selected for further processing. The key data consists of these fields: Program Product Number or user program Appl_ID Alert Type Alert Description Source CPUNAME FAULT ACTION SPECIFICATION The portion that specifies the action to be taken for the selected alert. The fault action specification consists of these fields: Target CPUNAME Automation Threshold Notification Threshold Automation Interval Timer Notification Interval Timer SV-Parm Command When the fault manager reads and internally formats the table, all data is converted to the format necessary for accurate comparison with fields in the generic alert. ΓòÉΓòÉΓòÉ 8.3.8.1.1. Program Product Number or User Program Appl_ID ΓòÉΓòÉΓòÉ Enter the program product number or the program Appl_ID as seven ASCII characters. If the program that requested that the alert be built is an IBM program product or the IBM LAN Management Utilities/2, enter the program product number. If the program that requested that the alert be built is a user-written program that uses the API described in Alert Generation and Routing, enter the program Appl_ID. The fault manager compares this table field to a field from the generic alert Product ID Subvector (X'10'). The fault manager uses the LAST occurrence of a Product ID Subvector that contains a Product Identifier Subvector (X'11'). Within this Subvector, the LAST occurrence of either a Software Program Product Number subfield (X'08') or a Software Product Serviceable Component ID subfield (X'02') is used. The fault manager uses the first 7 characters of this table entry field. If more than 7 are specified, the fault manager discards the record and writes a message to the LMU/2 log file. Because the record is discarded, the alerts it represents are forwarded. ΓòÉΓòÉΓòÉ 8.3.8.1.2. Alert Type ΓòÉΓòÉΓòÉ Enter the alert type as 2 ASCII characters. Valid values for each character are 0-3. VALUE MEANING 01 Permanent loss of availability 02 Temporary loss of availability 03 Performance -- below an acceptable level 11 Impending problem 12 Unknown The fault manager compares this data, converted, to the 4th byte of the Alert MS Subvector (X'92') in the generic alert. ΓòÉΓòÉΓòÉ 8.3.8.1.3. Alert Description ΓòÉΓòÉΓòÉ Enter 4 ASCII characters for the 4 hexadecimal digits that make up the alert description code point. Valid values for each character are 0-9, A-F. For example, enter the characters 360E for codepoint X'360E' (Modem Speeds Mismatch). VALUE MEANING 1xxx Hardware 2xxx Software 3xxx Communications 4xxx Performance 5xxx Congestion 6xxx Microcode 7xxx Operator 8xxx Specification 9xxx Intervention Required Axxx Problem Resolved Bxxx Notification Cxxx Security Fxxx Undetermined The fault manager compares this data, converted, to the 5th and 6th bytes of the Alert MS Subvector (X'92') in the generic alert. The 5th and 6th bytes of the Subvector identify code points that provide an index to predefined text describing the alert condition. ΓòÉΓòÉΓòÉ 8.3.8.1.4. Source CPUNAME ΓòÉΓòÉΓòÉ If the source CPU is an IBM OS/2 LAN Requester, enter the COMPUTERNAME that is in the IBMLAN.INI file in the alert-generating station. If the source CPU is a Novell NetWare Requester for OS/2, enter the internetwork address of the alert-generating station. Enter the wild card string of eight asterisks (********) to process this alert for all source stations. The fault manager compares this data to a field from the Hierarchy Resource List Subvector (X'05') in the generic alert. The last Resource List subfield (X'10') of type X'83' (CPU) is used by fault manager as it identifies the resource at which the alert condition occurred. It is important that the COMPUTERNAME in the IBMLAN.INI file be no more than 8 characters in length, as some OS/2 subsystems and applications use this value when creating a generic alert at a workstation. ΓòÉΓòÉΓòÉ 8.3.8.1.5. Target CPUNAME ΓòÉΓòÉΓòÉ This is the workstation on which the automation command is to be executed. This station must be running LMUCLI, and may be the station that is the source of the alert, an administrator workstation, or any other station that is running LMUCLI. For an IBM OS/2 LAN Requester, enter the COMPUTERNAME that is in the IBMLAN.INI file in the workstation on which the automation command is to be executed. For a Novell NetWare Requester, enter the internetwork address of the workstation on which the automation command is to be executed. If the command should be routed to the resource from which the alert was generated, enter the wild card string of eight asterisks (********). ΓòÉΓòÉΓòÉ 8.3.8.1.6. Automation Threshold ΓòÉΓòÉΓòÉ This specification, in conjunction with the Automation Interval Timer, determines if and when the automation routine specified in the Command field of the entry is invoked. The automation threshold specification is a string of 5 consecutive bytes (characters) that indicate when and how often to invoke an automation command. BYTES VALUE 1-2 ASCII 00. 3-4 Two-byte ASCII representation of hexadecimal value of automation threshold. 00-FE Invoke automation at this occurrence of the alert (for example, 10 means invoke automation the 16th time a generic alert matches the key data in this line). FF NEVER automate. The values 00 and 01 have the same meaning: invoke automation at every match to the key data. 5 Counter reset indicator. Y Reset Automation counter to zero when threshold is met. Results in automation every nth match to the key data (for example, every 10th match). N Do not reset the automation counter. Results in automation at the nth match to the key data and every match thereafter (for example, at the 10th, 11th, 12th... alert). See Automation/Notification Examples for examples of use. ΓòÉΓòÉΓòÉ 8.3.8.1.7. Notification Threshold ΓòÉΓòÉΓòÉ The notification threshold specification is a string of 5 consecutive bytes (characters) that indicate, in conjunction with the Notification Interval Timer, when and how often to forward an alert to NetView or IBM LAN Network Manager. Note: The alert destination is specified in the command to start AUECATCH. BYTES VALUE 1-2 ASCII 00. 3-4 Two-byte ASCII representation of hexadecimal value of automation threshold. 00-FE Forward the alert at this occurrence of the alert (for example, 10 means forward the alert the 16th time a generic alert matches the key data in this line). FF NEVER forward. The values 00 and 01 have the same meaning: forward the alert at every match to the key data. 5 Counter reset indicator. Y Reset notification counter to zero when threshold is met. Results in forwarding the alert every nth match to the key data (for example, every 10th match). N Do not reset the notification counter. Results in forwarding the alert at the nth match to the key data and every match thereafter (for example, at the 10th, 11th, 12th... alert). See Automation/Notification Examples for examples of use. ΓòÉΓòÉΓòÉ 8.3.8.1.8. Automation Interval Timer ΓòÉΓòÉΓòÉ The automation interval timer is a string of 1 - 4 decimal digits that indicates the time period, in minutes, within which the automation threshold must be reached before automation is invoked. It is the "five minutes" portion of "Invoke an automated routine if we get three of these alerts within a period of five minutes.", for example. The range is 0 - 1440 minutes. A value of 1440 represents one day. A value of 0 means there is no time limit for the automation threshold. The time interval begins with the first occurrence of the alert, or the first occurence of the alert after the previous interval has elapsed. See Automation/Notification Examples for examples of use. ΓòÉΓòÉΓòÉ 8.3.8.1.9. Notification Interval Timer ΓòÉΓòÉΓòÉ The notification interval timer is a string of 1 - 4 decimal digits that indicates the time period, in minutes, within which the notification threshold must be reached before the alert is forwarded to NetView or a LAN management functional address. It is the "five minutes" portion of "Forward the alert if we get three of these alerts within a period of five minutes.", for example. The range is 0 - 1440 minutes. A value of 1440 represents one day. A value of 0 means there is no time limit for the notification threshold. The time interval begins with the first occurrence of the alert, or the first occurence of the alert after the previous interval has elapsed. See Automation/Notification Examples for examples of use. ΓòÉΓòÉΓòÉ 8.3.8.1.10. (Examples of automation and notification thresholds with interval timers) ΓòÉΓòÉΓòÉ 0005Y 0005Y 0 0 - Invoke the automation routine every 5th occurrence of this alert. - Forward every 5th occurrence of this alert. 0005Y 0005Y 10 10 - If this alert occurs 5 or more times within a 10-minute interval, invoke the automation routine every 5th occurrence of this alert during the interval. - If this alert occurs 5 or more times within a 10-minute interval, forward every 5th occurrence of this alert during the interval. 0001Y 000AN 0 0 - Invoke the automation routine at every occurrence of this alert. - Forward the alert on the 10th occurrence and every occurrence thereafter. 0001Y 000AN 0 60 - Invoke the automation routine at every occurrence of this alert. - Forward the alert on the 10th occurrence each hour and every occurrence thereafter within that hour. 00FFN 0000N 0 0 - Never invoke the automation routine. - Always forward the alert. ΓòÉΓòÉΓòÉ 8.3.8.1.11. SV-Parm ΓòÉΓòÉΓòÉ This identifies a subvector from which data is to be collected and passed to the automation routine as parameters. Use 00 unless you specifically want the subvector text to be passed to the command specified in the Command field. Valid values are the following 2-byte ASCII strings: SUBVECTOR MEANING 93 Pick up Probable Cause data 94 Pick up User Causes data 95 Pick up Install Causes data 96 Pick up Failure Causes data 00 Do not pick up subvector data Within the subvector specified, the fault manager looks for the first instance of a Detailed Data Subfield (X'82') and appends the contents to the command specified in the Command field of this table. When processed by the automation routine, the appended data is a zero-terminated ASCII string of up to 44 bytes in length. Note: When the tokens -&t and -&c are used in the command, the location of the SV-parm text changes within the command string. See the Command topic for details. Use the ASCII string 00 if a subfield 82 is not expected in the alert or if you do not wish to pass the subfield 82 data to the automation routine. If SV-Parm is not 93-96 or 00, it is reset to 00, a message is written to the LMU/2 log file, and processing for the record continues. ΓòÉΓòÉΓòÉ 8.3.8.1.12. Command ΓòÉΓòÉΓòÉ This is the command and parameters to execute on the target node specified by the Target CPUNAME entry. This can be the name of a batch (.CMD) file that is accessible to the target node. The LMU/2 command transport is used to route the command; therefore, the target node must be running the LMUCLI software. There are two tokens that can be used in this field: o -&t Substitute the SV-Parm subfield 82 text wherever this token appears. o -&c Substitute the source computer name (computername or internetwork address, as appropriate) wherever this token appears. The tokens can be used in the command string multiple times, if desired. If you use either token, you should use both tokens; use of either token shuts off the normal automatic placement of both the SV-Parm text and the computer name. Because the LMU/2 command transport initiates this command using the standard OS/2 command line interface, any special symbols in the command string or in the data passed from the SV-Parm subvector may be misinterpreted by the OS/2 command shell (< and > become redirection, | becomes a pipe, and so forth). To use the symbols as literal symbols ( > as "greater than", | as "logical or", for example), place a double quote (") in the command string prior to the occurrence of the first symbol. If the symbols occur in the SV-Parm data only, place the double quote at the end of the command string. Alerts from PERFWACH, OSRWATCH, and SRVWATCH contain special symbols. If you specify an automation routine for those alerts, place a double quote in the command string as described above. Note: If it is used, the double quote is passed as part of the parameter string. Make sure the automation routine you specify in the Command field can parse the double-quote. Due to OS/2 command line length limitations, this field has a maximum of 132 characters. Whatever follows the command on the line is assumed to be parameters for the command. Do not attempt to add comments or other information following the command. ΓòÉΓòÉΓòÉ 8.3.8.2. Identical Keys in Table ΓòÉΓòÉΓòÉ You may specify multiple table entries with identical key data. If the generic alert being processed by the fault manager is matched by multiple table entries, all those matched entries will be processed. In this case, ALL automation thresholds that are met will cause the specified command to be executed on the target machine, and ANY notification threshold that is met will cause the alert to be forwarded. ΓòÉΓòÉΓòÉ 8.3.8.3. Sample Alerts Table ΓòÉΓòÉΓòÉ A sample alerts table is provided on the LMU/2 installation diskette and is named AUEUSER.SMP. You can edit this file, make the changes necessary for your installation, and save it under a name of your choice. Be sure to specify the name and location of the file in the LMU.INI file. ΓòÉΓòÉΓòÉ 8.3.8.4. Alerts Table Examples ΓòÉΓòÉΓòÉ An example of several alerts table entries follows: 5799PYA 02 2100 SERVER1 ******** 0001Y 0001Y 0 0 96 c:\recover\proc1 5799PYA 01 2100 SERVER1 MYCPU 0001Y 0001Y 0 0 96 c:\recover\proc1 5799PYA 02 4000 SERVER1 YOURCPU 0002N 0010Y 5 0 94 e:\perf\proc42 " MYAPPL 11 A000 SERVER2 AUTOCPU 0000Y 0000Y 3 3 94 z:\auto\audit102 alrtsam 01 2100 *** :10005A9575CF 0000Y 0000Y 0 0 96 c:\autotest.cmd Message: -&t from computer: -&c. ΓòÉΓòÉΓòÉ 8.3.9. LMU/2 Generic Alerts ΓòÉΓòÉΓòÉ The following table summarizes the generic alerts created by the LMU/2 programs. Component Type (CP) Description (CP) SV Message Text ---------------------------------------------------------------------------- LMUSRV TEMP 02 PROBLEM A000 94 LMU0900I Initialization complete RESOLVED LMUSRV TEMP 02 SOFTWARE 2100 94 LMU0901I Termination complete PROGRAM LMUSRV TEMP 02 PROBLEM A000 94 LMU0902I Initial heartbeat received RESOLVED LMUSRV TEMP 02 SOFTWARE 2100 94 LMU0903I Terminating heartbeat received PROGRAM LMUSRV PERM 01 SOFTWARE 2100 96 LMU0904W Heartbeat overdue PROGRAM LMUSRV PERM 01 CONFIGURATION 8000 94 LMU0905I Configuration changed ERROR ---------------------------------------------------------------------------- LMUCLI PERM 01 INTERVENTION 9000 96 LMU1093W LMUCLI initialization error REQUIRED ---------------------------------------------------------------------------- PERFWACH IMPD 11 PERFORMANCE 4000 94 LMU5101I PROC active > (thresh) PERFWACH IMPD 11 PERFORMANCE 4000 94 LMU5102I DISK active > (thresh) PERFWACH IMPD 11 PERFORMANCE 4000 94 LMU5103I SWAP active > (thresh) PERFWACH IMPD 11 PERFORMANCE 4000 94 LMU5104I FREE memory < (thresh) PERFWACH IMPD 11 PERFORMANCE 4000 94 LMU5105I TCPU utiliz > (thresh) ---------------------------------------------------------------------------- OSRWATCH TEMP 02 PERFORMANCE 4000 94 LMU5201I NCBS at (rqstr) < (thresh) (data) OSRWATCH TEMP 02 PERFORMANCE 4000 94 LMU5202I NSES at (rqstr) < (thresh) (data) OSRWATCH TEMP 02 PERFORMANCE 4000 94 LMU5203I NERR at (rqstr) >= (thresh) (data) OSRWATCH TEMP 02 PERFORMANCE 4000 94 LMU5204I NABT at (rqstr) >= (thresh) (data) OSRWATCH TEMP 02 PERFORMANCE 4000 94 LMU5205I NDTO at (rqstr) >= (thresh) (data) OSRWATCH TEMP 02 PERFORMANCE 4000 94 LMU5206I NLGN at (rqstr) >= (thresh) (data) OSRWATCH TEMP 02 PERFORMANCE 4000 94 LMU5207I NBFX at (rqstr) >= (thresh) (data) OSRWATCH TEMP 02 PERFORMANCE 4000 94 LMU5208I NDTI at (rqstr) >= (thresh) (data) OSRWATCH TEMP 02 PERFORMANCE 4000 94 LMU5209I NDT1 at (rqstr) >= (thresh) (data) ---------------------------------------------------------------------------- SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5310I SAVR at (srvr) > (thresh) (data) SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5311I SRBF at (srvr) >= (thresh) (data) SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5312I SBBF at (srvr) >= (thresh) (data) SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5313I TSES at (srvr) >= (thresh) (data) SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5314I TCON at (srvr) >= (thresh) (data) SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5315I TOPN at (srvr) >= (thresh) (data) SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5316I SSES at (srvr) >= (thresh) (data) SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5317I SCON at (srvr) >= (thresh) (data) SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5318I SOPN at (srvr) >= (thresh) (data) SRVWATCH PERF 03 PERFORMANCE 4000 94 LMU5319I SIDL at (srvr) >= (thresh) (data) ---------------------------------------------------------------------------- VIRALERT IMPD 11 SECURITY C000 94 AUE0070W Potential Virus Detected ---------------------------------------------------------------------------- DOSVIRGA IMPD 11 SECURITY C000 94 AUE0070W Potential Virus Detected ---------------------------------------------------------------------------- APPWATCH PERM 01 SOFTWARE 2100 96 LMU4790W (Count) instance(s) of (appl) PROGRAM ---------------------------------------------------------------------------- IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7040W CFRF at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7041W CIPC at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7042W CMPC at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7043W COSF at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7044W CRPC at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7045W CSPC at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7050W DFRF at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7051W DIPC at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7052W DMPC at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7053W DOSF at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7054W DRPC at (value) >= (thresh) IPXWATCH PERF 03 PERFORANCE 4000 94 LMU7055W DSPC at (value) >= (thresh) ---------------------------------------------------------------------------- NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7180W IAEC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7181W ICFC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7182W IFRF at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7183W IGFC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7184W IGRC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7185W ILEC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7186W IMPC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7187W IOSF at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7188W IPAC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7189W ISPC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7190W SACC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7191W SBIC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7192W SBLC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7193W SBSC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7194W SDPC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7195W SECF at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7196W SECR at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7197W SIPC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7198W SLCF at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7199W SLCR at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7200W SLPC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7201W SMUC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7202W SNLC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7203W SSFC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7204W SSPC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7205W SWCC at (value) >= (thresh) NWRWATCH PERF 03 PERFORANCE 4000 94 LMU7206W SWDC at (value) >= (thresh) ---------------------------------------------------------------------------- VOLWATCH IMPD 11 PERFORMANCE 4000 94 VOL0006I (Volume) AVB at (%) (thresh %) VOLWATCH IMPD 11 PERFORMANCE 4000 94 VOL0007I (Volume) ADS at (%) (thresh %) VOLWATCH IMPD 11 PERFORMANCE 4000 94 VOL0008I (Volume) PGB at (%) (thresh %) VOLWATCH IMPD 11 PERFORMANCE 4000 94 VOL0009I (Volume) Dismounted ---------------------------------------------------------------------------- NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0006I Server Utilization at (%) (thresh %) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0007I File Opens at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0008I File Creates at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0009I File Renames at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0010I File Deletes at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0011I Directory Searches at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0012I File Reads at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0013I File Writes at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0014I File Bytes Read at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0015I File Bytes Written at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0016I FAT Sectors Dirty at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0017I FAT Sectors Written at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0018I Packets Received at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0019I Packets Transmitted at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0020I Bytes Received at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0021I Bytes Transmitted at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0022I Packets Routed at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0023I Record Locks at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0024I Transactions at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0025I Average Connections at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0026I Peak Connections at (val) (thresh) NSVWATCH IMPD 11 PERFORMANCE 4000 94 NSV0027I Peak Utilization at (val %) (thresh %) ---------------------------------------------------------------------------- exmp. Note: The Program Product number for the IBM LAN Management Utilities/2 is 5799PYA. If you create Fault Manager alert table entries for any of the above alerts, specify that number as the first field in the entry. The second field, Alert Type, would be the value under the (CP) or codepoint column associated with Type. The third field would be the value under the (CP) or codepoint column associated with Description. If you wish to have the message text passed to an alert automation routine, specify the value under the SV column as the value in the SV-PARM field of the table entry; otherwise, specify 00 as the value in the SV-PARM field. ΓòÉΓòÉΓòÉ 8.3.10. LMUPOPUP ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUPOPUP ΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ ["string1"] ΓöÇΓöÇΓöÇ "string2" ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇ /R ΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇ /Ii ΓöÇΓöÇΓöÿ Options: /R Display both OK and CANCEL buttons, and set return code to 0 for OK, 1 for CANCEL /Ii Display an icon in the message box. Acceptable values for i: i Information q Question w Warning e Error [string1] Title to go in message box string2 Text to go in message box LMUPOPUP Syntax Use the LMUPOPUP command to display a popup window on a workstation. The LMUPOPUP command can be part of the command string in an LMUCMD command or in the alerts table, giving you the ability to send popup messages to a remote workstation directly or as part of a fault management automation routine. Be sure to enclose each string in double-quotes. o String1 is optional and, if used, is the title to go on the popup window. o String2 is required; it is the text of the message that is to be displayed in the popup window. LMUPOPUP Syntax Use the LMUPOPUP command to display a popup window on a workstation. The LMUPOPUP command can be part of the command string in an LMUCMD command or in the alerts table, giving you the ability to send popup messages to a remote workstation directly or as part of a fault management automation routine. Be sure to enclose each string in double-quotes. o String1 is optional and, if used, is the title to go on the popup window. o String2 is required; it is the text of the message that is to be displayed in the popup window. ΓòÉΓòÉΓòÉ 8.3.11. LMUPAGER ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUPAGER ΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Pageid ΓöÇΓöÇΓöÇΓöÇΓöÇ Message ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Help information Pageid 'Nickname' of person to page. Message Text to send to pager. Must be in double quotes (") if the text contains spaces or any special characters. LMUPAGER Syntax Use LMUPAGER in the command string of an entry in the user-defined alerts table, to send a page, or electronic message, to a pager, or message receiver, in response to an alert. The pager must support the IXO, SkyTel, or Motorola Peopfind protocol. The target computer on which LMUPAGER executes must have a modem operating. LMUPAGER requires 2 files in the directory where LMUPAGER.EXE resides: PAGESYS.DAT Identifies the paging systems (name, telephone number, line speed, and so forth) you may be calling PAGEUSR.DAT Defines the nicknames associated with the pager IDs, and specifies which paging system to use. Parameters: o The pageid parameter is required, and must be a nickname specified in the PAGEUSR.DAT file. Maximum size is 10 characters. o The message parameter is the text of the message you want to send; maximum length is determined by the paging system used. The message must be enclosed in double-quotes if the text contains any blanks or special characters. Example alert table entry using LMUPAGER. 5799PLX 11 C000 SERVER1 MODEMCPU 0000N 0010Y 0 0 00 lmupager johnj "Virus detected again--call immediately." ΓòÉΓòÉΓòÉ 8.3.11.1. PAGESYS.DAT ΓòÉΓòÉΓòÉ To identify the paging systems to be used with LMUPAGER, create a PAGESYS.DAT file, as follows: 1. Copy the sample LMU/2 PAGESYS.SMP file to PAGESYS.DAT. 2. Edit PAGESYS.DAT to contain a list of paging systems, their characteristics, and their phone numbers. Use one paging system per line, beginning in column 1 as follows: o Name to identify the paging system -- 10 characters. o One space o Protocol -- 8 characters. Must be IXO, SkyTel, or Peopfind. o One space o Port -- 1 digit. 1 - COM1 2 - COM2 o One space o Baud -- 5 digits. Modem speed required by the paging system used, in bits per second (300, 1200, 2400, and so forth). o One space o Parity --1 character. O - Odd E - Even N - None o One space o Data bits -- 1 digit. 7 or 8. o One space o Stop bits -- 1 digit. 1 or 2. o One space o Phone number -- 23 characters. Include all access digits, area code, and dashes between digits. Example: 9-1-919-555-4033 o One space o Login -- Applies to SkyTel protocol only. 10 characters. If used, is the Tymnet login. Requires a Tymnet password in the next field. o One space o Password -- Applies to SkyTel protocol only. 10 characters. If used, is the Tymnet password. Requires a Tymnet login in the previous field. Note: All fields are left-adjusted and padded with blanks to the right except Baud, which is right-adjusted and padded with blanks to the left. See PAGESYS.SMP for an example. In addition to PAGESYS.DAT, you must also create a PAGEUSR.DAT file to assign a userid or nickname to each pager. ΓòÉΓòÉΓòÉ 8.3.11.2. PAGEUSR.DAT ΓòÉΓòÉΓòÉ To assign a nickname to a pager to be called with LMUPAGER, create a PAGEUSR.DAT file, as follows: 1. Copy the sample LMU/2 PAGEUSR.SMP file to PAGEUSR.DAT. 2. Edit PAGEUSR.DAT to contain a list of pagers and the nickname you assign to each. Use one pager per line, as follows: o Nickname -- Name to use to identify the pager or person. 10 characters. This is the name that will be used in LMUPAGER commands to identify the pager. o One space o Name of a paging system -- 10 characters. Must match a name you assigned in positions 1-10 of a line in the PAGESYS.DAT file. o One space o Pager ID -- 9 characters. Must be the ID that is built into the pager you want to reach. ΓòÉΓòÉΓòÉ 8.3.12. LMUPAGE ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUPAGE ΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Pageid ΓöÇΓöÇΓöÇ Message ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Help information Pageid 'Nickname' of person to page. Message Text to send to pager. The combined length of Pageid and Message can not exceed 41 characters. Message must be enclosed in double quotes (") if it contains OS/2 command operator characters ( ><|()^% ). LMUPAGE Syntax LMUPAGE is a command line interface to LMUPAGER, to generate a page, or electronic message, from an OS/2 workstation. LMUPAGE generates an LMUPAGE alert, for which you must set up an entry in the user-defined alerts table. The program product number in the entry must be LMUPAGE, and the command string must specify LMUPAGER -&t as in the following example. See the alerts table format section for an explanation of an alert table entry. LMUPAGE 02 A000 * MODEMCPU 0000Y 00FFY 0 0 94 lmupager -&t All conditions for LMUPAGER apply; for example, the target computer must have a modem running. See the description of LMUPAGER for details. Parameters: o The pageid parameter is required, and must be a nickname specified in the PAGEUSR.DAT file. Maximum size is 10 characters. o The message parameter is the text of the message you want to send; maximum length of both the pageid and the message together is 41 characters. The message must be enclosed in double-quotes if the text contains any blanks or special characters. The pageid and message text are appended to the LMUPAGER command in the alerts table entry and are sent to the target computer specified in the entry. ΓòÉΓòÉΓòÉ 8.4. Query/Terminate ΓòÉΓòÉΓòÉ Use LMUQUERY to query LMU/2 programs in a station or to terminate them. Use SHUTDOWN to terminate all functions in a workstation and, optionally, to restart the workstation. ΓòÉΓòÉΓòÉ 8.4.1. LMUQUERY ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUQUERY ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ * ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ /T[F] ΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ AUECATCH ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ AUEPITCH ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ AUERECVR ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUCLI ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUGUI ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUSRV ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Help information /T[F] Terminate specified LMU/2 program(s); use [F]orce to SIGTERM LMU/2 program(s) * Query (or terminate) all LMU/2 programs AUECATCH Query/terminate AUECATCH AUEPITCH Query/terminate AUEPITCH AUERECVR Query/terminate AUERECVR LMUCLI Query/terminate LMUCLI LMUGUI Query/terminate LMUGUI LMUSRV Query/terminate LMUSRV LMUQUERY Help The LMUQUERY command can be run from the command line of a workstation or as the command string in an LMUCMD command. The LMUQUERY command queries the workstation in which it is running to determine whether the specified LMU/2 programs are running. Optionally, the LMUQUERY command can terminate the specified LMU/2 programs. Any combination of AUECATCH, AUEPITCH, AUERECVR, LMUCLI, LMUGUI, or LMUSRV may be specified. Parameters: o The /t option causes LMUQUERY to terminate the selected LMU/2 programs. The default is to query only. o The * option specifies all of the programs AUECATCH, AUEPITCH, AUERECVR, LMUCLI, LMUGUI, and LMUSRV. o AUECATCH - query or terminate AUECATCH.EXE in the workstation. o AUEPITCH - query or terminate AUEPITCH.EXE in the workstation. o AUERECVR - query or terminate AUERECVR.EXE in the workstation. o LMUCLI - query or terminate LMUCLI.EXE in the workstation. o LMUGUI - query or terminate LMUGUI.EXE (the graphical user interface) in the workstation. o LMUSRV - query or terminate LMUSRV.EXE in the workstation. Examples: o To query AUEPITCH and LMUCLI: LMUQUERY AUEPITCH LMUCLI o To terminate AUEPITCH and LMUCLI: LMUQUERY /t AUEPITCH LMUCLI o To query AUECATCH, AUEPITCH, AUERECVR, LMUCLI, LMUGUI, and LMUSRV: LMUQUERY * or LMUQUERY AUECATCH AUEPITCH AUERECVR LMUCLI LMUGUI LMUSRV o To terminate AUECATCH, AUEPITCH, AUERECVR, LMUCLI, LMUGUI, and LMUSRV: LMUQUERY /t * or LMUQUERY /t AUECATCH AUEPITCH AUERECVR LMUCLI LMUGUI LMUSRV ΓòÉΓòÉΓòÉ 8.4.2. SHUTDOWN ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ SHUTDOWN ΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /B[min] ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Options: ? Help information /B[min] re-Boot, after waiting min minutes If only /B is specified, computer will re-boot immediately SHUTDOWN terminates all applications, closes down the file system and optionally re-boots the computer. SHUTDOWN Help Information The /b option tells the station to re-IPL after shutting down. The number following the /b is the time in minutes to wait after shutting down, before re-IPLing. If no number follows the /b, the station re-IPLs immediately after shutting down. Note: The /b option requires the LMUIPL.SYS device driver in the managed system that is to be shut down. Be sure the CONFIG.SYS file in the managed system contains the DEVICE=drive:\path\LMUIPL.SYS statement. A /b15, for instance, tells the station to re-IPL 15 minutes after shutting down. This option is useful in connection with an uninterruptible power supply (UPS). For example: If the managed computer is connected to a UPS and there is an electrical power outage, the UPS supplies power for a specific period of time, usually several minutes. At some time before the UPS power expires, the administrator workstation could send a SHUTDOWN command to the managed computer, specifying the /b option and a value that exceeds the remaining time the UPS can supply power. The managed system will shut down all applications and wait. If power returns before the UPS expires, the /b timer is still operational, and at the expired time the managed system will re-IPL. If the UPS expires and power has not returned, the managed system has already been shut down safely and no data has been lost. SHUTDOWN is initiated by an LMUCMD command from an administrator workstation, or through the managed computer command line interface. o If the SHUTDOWN command is invoked by the LMUCMD command, a pop-up panel is presented on the managed station display to notify a user at the managed station that a shutdown command has been issued for the station. The user has the opportunity to override the shutdown by selecting the Cancel pushbutton before 20 seconds elapse. o If the SHUTDOWN command is invoked from the command line of a station, the station shuts down immediately; there is no opportunity to cancel the shutdown. Warning The SHUTDOWN command does not ask for confirmation at the managed station. It requires no user response. Sessions in progress will be shut down-data may be lost. There will be no "Are you sure?" messages. ΓòÉΓòÉΓòÉ 9. Management Applications (DOS) ΓòÉΓòÉΓòÉ Gathering Vital Product Data To collect vital product data (configuration data) for a DOS workstation, use: QDOSVPD to collect configuration data for the DOS workstation in which it runs, and optionally to send the data to an LMU/2 database. QDOSVPD is discussed in the topic QDOSVPD. Monitoring Performance To monitor workstations attached to a Novell NetWare file server, use: NWRWATCH in a DOS workstation logged in to a NetWare file server, to monitor the statistics for Novell's Internetwork Packet Exchange (IPX) protocol and Sequenced Packet Exchange (SPX) protocol for every workstation attached to that NetWare file server, and to send generic alerts to the fault management system when specific conditions occur. NWRWATCH is discussed in the topic NWRWATCH. Fault Management To handle local fault conditions, use: AUEDOSAL in the DOS client computer to generate local alerts that will be forwarded to the fault manager. AUEDOSAL is discussed in topic AUEDOSAL. For a list of the alert types processed by AUEUSRGA and AUEDOSAL, see Error Number Mappings. To send an alert to the fault manager after a virus-checking program detects a potential virus in a workstation, use: DOSVIRGA on a managed DOS Station. An operator or user-written .BAT file must determine when to run DOSVIRGA. DOSVIRGA is discussed in topic DOSVIRGA. DOS Heartbeat To indicate the presence of a DOS workstation to the graphical user interface, use: LMUDOSHB on a managed DOS Station. LMUDOSHB issues an initial heartbeat to the managing system. Optionally, LMUDOSHB can issue a terminating heartbeat. LMUDOSHB is discussed in topic LMUDOSHB. ΓòÉΓòÉΓòÉ 9.1. Vital Product Data (DOS Workstations) ΓòÉΓòÉΓòÉ Vital Product Data consists of configuration data about the workstation. To gather configuration data about a DOS workstation, see QDOSVPD. To see the configuration data tables in the LMU/2 database, see the topic LMU/2 Database Tables. ΓòÉΓòÉΓòÉ 9.1.1. QDOSVPD ΓòÉΓòÉΓòÉ Note: QDOSVPD executes in a DOS machine only; it does not run in the DOS session of an OS/2 machine. In a Novell NetWare Server, QDOSVPD runs only before the NetWare Server is started, or after the NetWare Server has been shut down. ' ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ QDOSVPD ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ +O[filespec] ΓöÇΓöñ Γö£ΓöÇ +K[path] ΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +A ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +P ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ +Wpath ΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +Q ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓöÿ Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +D ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +S ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +Rdestination ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇ -S ΓöÇΓöÿ Option Description: ? Displays this help panel. +A Displays the recognized Micro Channel adapters. +D Provides a more detailed description of most items within each category. (Example: ROM and RAM memory addresses by adapter). +S Provides SYSLEVEL file processing (searching and reporting). +O[filespec] Allows the redirection of display to QDOSVPD.DAT in the current directory. Optional 'filespec' overrides filename and location to receive the report. +P Pauses the display after each screen of output. +Q Turns off display of copyright information. +Rdestination Transmits vital product data to 'destination'. (1 to 21 characters specifing the computer name or internetwork address of the LMU/2 managing system with database). Note: All categories of data are collected. -S Suppresses SYSLEVEL file processing (See +R option). +Wpath Specifies the location of the QDOSVPD working directory. +K[path] Saves vital product data in the current directory for later use by the QUERYVPD.NLM program. Optional 'path' allows an alternate directory to be specified. Note: Intended for NetWare* file servers only. * NetWare and Novell are registered trademarks of the Novell corporation. QDOSVPD Syntax The QDOSVPD program collects vital product data (configuration data) about the DOS machine in which it is executing. It is designed to be run both as a standalone utility and as part of LMU/2. As a standalone utility, QDOSVPD displays vital product data at the console or redirects it to a file. As part of LMU/2, QDOSVPD: o Sends the vital product data to the database machine specified by the /r option or redirects it to a file specified by the /o option o In a Novell NetWare Server machine, optionally saves the vital product data in a file for later use by the QUERYVPD.NLM program. LAN Management Utilities/2 Database Tables identifies the vital product data recorded by the LMU/2 database. Data from the following optional user-defined files is included in the vital product data captured by QUERYVPD: o USERVPD.DAT o ADAPTERS.DEF o CRITFILE.DEF Options: o The ? option produces the help panel. o The +a option displays the list of Micro Channel* adapters recognized by the QDOSVPD program. This includes the adapters identified in the ADAPTERS.DEF file. o The +d option provides additional, more detailed, information to the QDOSVPD console output, such as the following: - More detailed memory and disk information - More detailed logical disk information - POS data (Micro Channel machine only) - Planar ID (Micro Channel machine only) - The location of the CRITFILE.DEF file and USERVPD.DAT file used , if the files were found. o The +s option produces SYSLEVEL information (information from any program-associated user-generated SYSLEVEL.xxx file that may be in the DOS machine). o The +r option redirects the QDOSVPD output to a managing system with database (database machine), for inclusion in an LMU/2 database. Destination must be one of the following: - For an IBM DOS LAN Requester managed system, the requester ID of the database machine (COMPUTERNAME in the IBMLAN.INI file in the database machine) - For a Novell NetWare Requester for DOS managed system, the internetwork address ([network number]:node address) of the database machine. The data sent includes hardware, logical drives, user-defined data (from the USERVPD.DAT file), information about the files specified in the CRITFILE.DEF file and any SYSLEVEL.xxx files. o The -s option is used in conjunction with the +r option; it suppresses the search for SYSLEVEL information, reducing the processing time for QDOSVPD and eliminating SYSLEVEL information from the data sent to the managing system with database. QDOSVPD +rRTSRV101 -s o The +o option redirects the formatted output to a file. The default filename is QDOSVPD.DAT in the current directory on the managed computer. o The +p option causes the display of output to pause after each screenful of data. o The +q option suppresses the display of copyright information. o The +k option specifies a DOS directory in which to save vital product data for later use by the QUERYVPD.NLM program. The default is the current directory. This option applies only to a station that will be running the Novell NetWare file server after QDOSVPD has completed. o The +wpath option specifies a location to search for the user-defined data files (USERVPD.DAT, ADAPTERS.DEF, CRITFILES.DEF). The location specified becomes the first place searched for these files. In the QDOSVPD parameters, a plus sign (+) and slash (/) are equivalent; a minus sign (-) and a tilde (~) are equivalent. Any +option can be specified as /option, and any -option can be specified as ~option. The r option, for example, can be specified as either +r or /r; the s option can be specified as either -s or ~s. The slash (/), plus sign (+), minus sign (-), and tilde (~) are processed left to right as they appear in the command. Of contradictory options, such as +s and -s, or -s and +r, the rightmost option prevails. As a general rule, any plus options should be specified first, followed by any minus options. Examples: QDOSVPD (no options) displays the following kinds of information: o Hardware o Operating system o Logical drives o User data (from the USERVPD.DAT file) o Critical file information (on files identified in the CRITFILE.DEF file) QDOSVPD /rdestination directs the following kinds of information to the LMU/2 database: o Hardware o Operating system o Logical drives o User data (from the USERVPD.DAT file) o Critical file information (on files identified in the CRITFILE.DEF file) o SYSLEVEL data (including current and previous corrective service diskette levels) Examples in NetWare Servers (might be placed in the AUTOEXEC.BAT file): QDOSVPD +kc:\lmu2 +q stores the vital product data in the C:\LMU2 directory for later use by the QUERYVPD.NLM program, and suppresses the display of copyright data. QDOSVPD /wc:\lmu2 searches C:LMU2 for USERVPD.DAT, CRITFILE.DEF, and ADAPTERS.DEF; if any of these are found, their data is included in the vital product data displayed at the console. Note that only Micro Channel adapters are recognized by QDOSVPD. ΓòÉΓòÉΓòÉ 9.2. Performance (DOS Workstations) ΓòÉΓòÉΓòÉ Using NWRWATCH provides protocol statistics monitoring for DOS workstations attached to a Novell NetWare file server. ΓòÉΓòÉΓòÉ 9.2.1. NWRWATCH ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ NWRWATCH ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Iiterations ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /Ssleep ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@IAECthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@ICFCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@IFRFthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@IGFCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@IGRCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@ILECthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@IMPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@IOSFthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@IPACthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@ISPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SACCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SBICthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SBLCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SBSCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SDPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SECFthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SECRthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SIPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SLCFthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SLCRthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SLPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SMUCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SNLCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SSFCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SSPCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SWCCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /@SWDCthreshold ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Where: ? Help information /Iiterations Statistics collection iterations; range is 0 to 65535 (use 0 to loop forever); default is 1 /Ssleep Sleep interval (in minutes) between iterations; range is 1 to 1440; default is 5 minutes /@IAECthreshold IPX AES Event Count /@ICFCthreshold IPX ECB Cancel Failure Count /@IFRFthreshold IPX Find Route Failure count /@IGFCthreshold IPX Get ECB Failure Count /@IGRCthreshold IPX Get ECB Request Count /@ILECthreshold IPX Listen ECB Count /@IMPCthreshold IPX Malformed Packet Count /@IOSFthreshold IPX Open Socket Failure count /@IPACthreshold IPX Postponed AES event Count /@ISPCthreshold IPX Send Packet Count /@SACCthreshold SPX Abort Connection Count /@SBICthreshold SPX Bad Incoming packet Count /@SBLCthreshold SPX Bad Listen packet Count /@SBSCthreshold SPX Bad Send packet Count /@SDPCthreshold SPX Suppressed (discarded) Packet Count /@SECFthreshold SPX Establish Connection Failure Count /@SECRthreshold SPX Establish Connection Request Count /@SIPCthreshold SPX Incoming Packet Count /@SLCFthreshold SPX Listen Connection Failure count /@SLCRthreshold SPX Listen Connection Request count /@SLPCthreshold SPX Listen Packet Count /@SMUCthreshold SPX Maximum Used Connection count /@SNLCthreshold SPX No session Listen ECB Count /@SSFCthreshold SPX Send Failure Count /@SSPCthreshold SPX Send Packet Count /@SWCCthreshold SPX Window Choke Count /@SWDCthreshold SPX Watchdog Destroy session Count Range of threshold values is 1 to 2147483647; default is "do not check" NWRWATCH Help Information NWRWATCH runs in a DOS workstation that is running the Novell NetWare Requester for DOS and is logged in to a Novell NetWare file server; it does not run in the DOS session of OS/2. NWRWATCH monitors the protocol statistics for every workstation (OS/2 or DOS) attached to the NetWare file server that the DOS workstation is logged in to, and generates a generic alert whenever a specified threshold is exceeded. The protocols monitored are the Internetwork Packet Exchange (IPX) and the Sequenced Packet Exchange (SPX). It is similar to OSRWATCH, but collects its statistics on NetWare Requester workstations. Parameters: o /iiterations - the number of times to poll the NetWare file server for statistical information o /ssleep - the time in minutes between each poll. o Thresholds - for each of the thresholds, generate a generic alert when the count for the event exceeds the threshold value you specify. In the threshold descriptions in the help panel, Event Control Block is indicated as ECB. The meaning of each of the thresholds is self-explanatory; see the Novell documentation on System Calls - DOS for details. NetWare statistics are cumulative from the time the NetWare Requester in each workstation is started; set your thresholds accordingly. ΓòÉΓòÉΓòÉ 9.3. Fault Management (DOS Workstations) ΓòÉΓòÉΓòÉ Using DOSVIRGA in a user batch file provides a virus-detection alert from a DOS workstation. Using LMUDOSHB in a managed DOS workstation provides an initial (or, optionally, terminating) heartbeat to the managing system. ΓòÉΓòÉΓòÉ 9.3.1. DOSVIRGA ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ DOSVIRGA ΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓöÇΓöÇ fault manager ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Options: fault manager Required. The name of the fault manager to process the alert. DOSVIRGA Syntax DOSVIRGA is intended to be run following a virus-detection program in a DOS workstation. When executed, DOSVIRGA builds a generic "virus detected" alert and sends the alert to the fault manager specified in the DOSVIRGA command. Note that the fault manager parameter is required. Parameter: o fault manager - the computer name of the machine running the fault manager software. For an IBM DOS LAN Requester, this name must be the requester ID of the fault manager computer (identified by COMPUTERNAME in the IBMLAN.INI file in the fault manager computer). For a Novell NetWare Requester for DOS, this name must be the internetwork address of the fault manager computer. DOSVIRGA does not itself detect the virus. It must be run only after a program is run that checks for the possible existence of a virus, and only if the program finds a potential virus. Its purpose is to alert the central site operator of the detected virus condition. It is the user's responsibility to set up the conditional logic to run DOSVIRGA. This can be done by using a .BAT file to: 1. Run the virus-checking program of your choice 2. Check the return code from the virus-checking program for a "virus detected" condition (generally, any non-zero return code) 3. Run DOSVIRGA only if a "virus detected" return code was returned. ΓòÉΓòÉΓòÉ 9.3.2. LMUDOSHB ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMUDOSHB ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ managing-system ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ /T ΓöÇΓöÇΓöÿ Where: ? Help information /T Send terminating heartbeat; default is to send initial heartbeat managing-system Managing system to receive heartbeat LMUDOSHB Syntax The LMUDOSHB program provides an initial heartbeat (only) for a DOS station, to notify the managing system that the DOS workstation is present on the network. Optionally, the LMUDOSHB program can be run with the /t parameter just before shutting down, to indicate to the managing system that the DOS workstation is leaving the network. For an IBM DOS LAN Requester, this command should be placed in the AUTOEXEC.BAT file or the PROFILE.BAT file. For a Novell NetWare Requester for DOS, this command should be placed in the NetWare login script. ΓòÉΓòÉΓòÉ 10. Management Applications (Novell NetWare Server) ΓòÉΓòÉΓòÉ Purposes The following section describes the types of LAN Management Utilities/2 (LMU/2) management applications for a Novell NetWare Server and the programs that are in each. Gathering Vital Product Data To gather vital product (configuration) data, use: QUERYVPD.NLM on a managed NetWare Server in conjunction with QDOSVPD. QUERYVPD.NLM is discussed in topic QUERYVPD.NLM. Monitoring Performance on the NetWare Server To monitor volume (disk) performance on the NetWare Server, use: VOLWATCH.NLM to collect volume data from the server disk and to generate generic alerts when thresholds are exceeded. VOLWATCH is discussed in topic VOLWATCH.NLM. NSVWATCH.NLM to collect performance data for the NetWare Server from the NetWare SS.NLM module, analyze the collected data for selected conditions, and send generic alerts to the fault management system when those conditions occur. NSVWATCH is discussed in topic NSVWATCH.NLM. General To access or verify the LMU/2 property values (control information) in the bindery, use: LMULOAD to view or change the LMU/2 control values in the bindery. LMULOAD is discussed in the topic LMULOAD. ΓòÉΓòÉΓòÉ 10.1. Vital Product Data (NetWare Server) ΓòÉΓòÉΓòÉ Vital Product Data consists of configuration data about the workstation. See: QUERYVPD.NLM. To gather configuration data about a Novell NetWare Server station. To see the configuration data tables in the LMU/2 database, see the topic LMU/2 Database Tables. ΓòÉΓòÉΓòÉ 10.1.1. QUERYVPD.NLM ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ QUERYVPD ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ Volume:path ΓöÇΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ? ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇ +O[filespec] ΓöÇΓöñ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +P ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé Γöé ΓööΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö┤ΓöÇΓöÇΓöÿ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +D ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ +Q ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇ +Ipath ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇ +Wpath ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇ +R[destination] ΓöÇΓöÇΓöÿ Option Description: ? Displays this help panel. +D Provides a more detailed description of most items within each category. (Example: ROM and RAM memory addresses by adapter). +Q Turns off display of copyright information. +Ipath Specifies the 'path' of the DOS directory containing saved vital product data from QDOSVPD. (Default: LMU2 DOS DIRECTORY). +Wpath Specifies the location of the QUERYVPD working directory within the NetWare partition. (Default: LMU2 INSTALL DIRECTORY). +R[destination] Transmits vital product data to the LMU/2 managing system with database. Optional 'destination' (1 to 21 characters) specifies an internetwork address. (Default: DATABASE MACHINE) Note: All categories of data are collected and sent. +O[filespec] Allows the redirection of display to QUERYVPD.DAT in the current directory. Optional 'filespec' overrides filename and location to receive report. +P Pauses the display after each screen of ouput. * NetWare and Novell are registered trademarks of the Novell corporation. QUERYVPD.NLM Syntax The QUERYVPD.NLM program is part of a two-step system to collect vital product data (configuration information) about the NetWare Server machine in which it is executing. The first step is to run QDOSVPD at system startup, with the +k option; the second step is to run QUERYVPD.NLM while DOS is still present in the machine, which retrieves the configuration data captured by the QDOSVPD program earlier, saves the data in the NetWare partition, and then solicits the Novell NetWare operating system for additional information. After the initial execution of QUERYVPD.NLM, DOS can be removed from the system. Subsequent executions of QUERYVPD.NLM retrieve the vital product data from the location in the NetWare partition if DOS is no longer present. QUERYVPD.NLM is designed to be run both as a standalone utility and as part of LMU/2. When QUERYVPD is run, vital product data can be displayed at the console, redirected to a file, or sent to a database machine and stored in an LMU/2 database. When QUERYVPD.NLM is initiated by the LMUCMD command, the vital product data console display can not be redirected back to the administrator workstation console. Vital Product Data Tables identifies the vital product data recorded by the LMU/2 database. Options: o The ? option produces the help panel. o The +d option provides additional, more detailed, information to the QUERYVPD console output, such as the following: - More detailed memory and disk information - More detailed logical disk information - POS data (Micro Channel machine only) - Planar ID (Micro Channel machine only) - The location of the CRITFILE.DEF file and USERVPD.DAT file used, if the files were found. o The +ipath option specifies the location of the DOS directory that contains the data file written by QDOSVPD. The default location is the LMU/2 DOS Directory (LMU_DOS_DIR) specified in the bindery. o The +wpath option specifies the location of a NetWare directory that QUERYVPD.NLM will search for the user-defined USERVPD.DAT and CRITFILE.DEF files. QUERYVPD.NLM does not search any other location for these files. This is also the location QUERYVPD.NLM uses to store the vital product data retrieved from the DOS partition while DOS is still present. The default location is the LMU/2 Install Directory (LMU2_HOME_DIR) specified in the bindery. o The +r option redirects the QUERYVPD output to a managing system with database (database machine) for inclusion in an LMU/2 database. The managing system with database must be running the Novell Requester for OS/2 and the appropriate LMU/2 software. Destination is optional but, if used, must be the internetwork address ([network number]:node address) of the database machine. If destination is not used, the output is directed to the computer identified as the database machine (M_WITH_DATABASE) in the managed NetWare Server's bindery; if destination is used, it overrides the specification in the bindery. The data sent includes hardware, disk drive volume information, user-defined data (from the USERVPD.DAT file), and information about the files specified in the CRITFILE.DEF file. o The +o option redirects the formatted output to a file. Filespec is optional; if used, any path specified must point to a location in the NetWare partition. Filespec is specified as volume:path\filename. The default filename is QUERYVPD.DAT in the current directory on the managed NetWare Server. In the QUERYVPD parameters, a plus sign (+) and slash (/) are equivalent: any +option can be specified as /option. The r option, for example, can be specified as either +r or /r. Examples: QUERYVPD (no options) displays the following kinds of information: o Hardware o Operating system o Logical drives o User data (from the USERVPD.DAT file) o Critical file information (on files identified in the CRITFILE.DEF file) QUERYVPD /r directs the same kinds of information to the LMU/2 database. Note that the only adapters reported are Micro Channel adapters. Search Order for QDOSVPD Data In order for QUERYVPD.NLM to work, QDOSVPD must run first and must save the vital product data in a file that QUERYVPD.NLM can access. The NetWare Server computer is customized to cause QDOSVPD with the +K option to run at each computer startup (see Customizing a Novell NetWare Server), to meet this requirement. QDOSVPD can be run any other time you desire in addition to system startup. When QUERYVPD.NLM looks for the data created by QDOSVPD, it searches the disks in the following order: 1. If DOS is still present in the system, QUERYVPD.NLM looks in the path specified by the /I option on the QUERYVPD.NLM command line; if no /I option was specified, QUERYVPD.NLM looks in the path specified by the LMU/2 DOS Directory property in the bindary. 2. If DOS is not present in the system, QUERYVPD.NLM looks in the path specified by the /W option on the QUERYVPD.NLM command line; if no /W option was specified, QUERYVPD.NLM looks in the path specified by the LMU/2 Install Directory property in the bindary. If QUERYVPD.NLM finds the vital product data file created by QDOSVPD, it copies the file to the NetWare partition (in the location specified by the /W option on the QUERYVPD.NLM command line; if no /W option was used, the file is copied to the location specified by the LMU/2 Install Directory property in the bindery). If QUERYVPD.NLM does not find the vital product data file, it issues an error message and terminates. ΓòÉΓòÉΓòÉ 10.2. Performance (NetWare Server) ΓòÉΓòÉΓòÉ Using VOLWATCH and NSVWATCH provides event monitoring (also called thresholding) of NetWare Server performance in order to generate generic alerts or event logging. ΓòÉΓòÉΓòÉ 10.2.1. VOLWATCH ΓòÉΓòÉΓòÉ VOLWATCH [?] [/I<iterations>] [/S<sleeptime>] [/D] [/R[internetaddress]] [/@AVB] [/@ADS] [/@PGB] [/@DISY] Where: ? Help information /I<iterations> Specifies the number of polling iterations to run. /S<sleeptime> Specifies the time in minutes to sleep between iterations. /D Display output to console /R[internetaddress] Send output to managing system with database at 'internetaddress' (optional). /@AVB Generate an alert to the fault manager if the percentage of available block space is below percent. /@ADS Generate an alert to the fault manager if the percentage of available directory slots is below percent. /@PGB Generate an alert to the fault manager if the percentage of purgeable block space is above percent. /@DISY Generate an alert to the fault manager if any volumes have been dismounted. VOLWATCH collects statistics about the disk volumes of a Novell NetWare Server. The data is collected at user-specified intervals and monitored for exceptions to user-specified thresholds. VOLWATCH accepts the following input parameters. Note that the < and > in the help information indicate user-supplied data and are not entered as part of the parameter. o /iiterations - the number of times to poll the NetWare file server for disk information. o /smin - the time in minutes between each poll. o /d - display the output at the NetWare Server console. o /r[internetaddress] - send the output to the managing system with database. Internetaddress is optional but, if used, is the internetwork address of the managing system with database. If internetaddress is not used, the data is sent to the database machine specified in the bindery. o /@avbp - monitor the available block space; if the percentage of available block space falls below the value specified for threshold n, generate a generic alert. n is a percentage, and is a number between 1 and 100. The alert generated is VOL0006I. o /@adsp - monitor the available directory slots; if the percentage of available directory slots falls below the value specified for threshold n, generate a generic alert. n is a percentage, and is a number between 1 and 100. The alert generated is VOL0007I. o /@pgbp - monitor the purgeable block space; if the percentage of purgeable block space falls below the value specified for threshold n, generate a generic alert. n is a percentage, and is a number between 1 and 100. The alert generated is VOL0008I. o /@disy - monitor the volumes that are mounted; if any volumes is dismounted, generate a generic alert. The alert generated is VOL0009I. The statistical data collected for each volume includes: o Volume name o Number of 512-byte sectors per block o Starting block o Total number of blocks o Number of available blocks o Total number of directory slots o Number of available directory slots o Maximum directory slots used o Hashing support indicator o Volume-removable indicator o Mounted/dismounted indicator o Number of purgeable (claimable) blocks ΓòÉΓòÉΓòÉ 10.2.2. NSVWATCH ΓòÉΓòÉΓòÉ Note: This command requires the SS.NLM module from Novell NetWare. , NSVWATCH [?] [/I<iterations>] [/L<length>] [/S<sleeptime>] [/D] [/R[internetaddress]] [/@SRU] [/@FIO<n>] [/@FIC<n>] [/@FIR<n>] [/@FID<n>] [/@DIS<n>] [/@FRE<n>] [/@FWI<n>] [/@FBR<n>] [/@FBW<n>] [/@FSD<n>] [/@FSW<n>] [/@PKR<n>] [/@PKT<n>] [/@BYR<n>] [/@BYT<n>] [/@PRT<n>] [/@RLO<n>] [/@TRA<n>] [/@CON<n>] [/@PCO<n>] [/@PSU<n>] Where: ? Help information /I<iterations> Specifies the number of polling iterations to run. /L<length> Length of time in minutes of each iteration. /S<sleeptime> Specifies the time in minutes to sleep between iterations. /D Display output to console /R[internetaddress] Send output to managing system with database at 'internetaddress' (optional). /@SRU Generate an alert to the fault manager if the percentage of server utilization is above percent. /@FIO<n> Generate an alert to the fault manager if the number of file opens is above <n>. /@FIC<n> Generate an alert to the fault manager if the number of file creates is above <n>. /@FIR<n> Generate an alert to the fault manager if the number of file renames is above <n>. /@FID<n> Generate an alert to the fault manager if the number of file deletes is above <n>. /@DIS<n> Generate an alert to the fault manager if the number of directory searches is above <n>. /@FRE<n> Generate an alert to the fault manager if the number of file reads is above <n>. /@FWI<n> Generate an alert to the fault manager if the number of file writes is above <n>. /@FBR<n> Generate an alert to the fault manager if the number of file bytes read is above <n>k. /@FBW<n> Generate an alert to the fault manager if the number of file bytes written is above <n>k. /@FSD<n> Generate an alert to the fault manager if the number of FAT sectors dirty is above <n>. /@FSW<n> Generate an alert to the fault manager if the number of FAT sectors written is above <n>. /@PKR<n> Generate an alert to the fault manager if the number of packets received is above <n>k. /@PKT<n> Generate an alert to the fault manager if the number of packets transmitted is above <n>k. /@BYR<n> Generate an alert to the fault manager if the number of bytes received is above <n>k. /@BYT<n> Generate an alert to the fault manager if the number of bytes transmitted is above <n>k. /@PRT<n> Generate an alert to the fault manager if the number of packets routed is above <n>. /@RLO<n> Generate an alert to the fault manager if the number of record locks is above <n>. /@TRA<n> Generate an alert to the fault manager if the number of transactions is above <n>. /@CON<n> Generate an alert to the fault manager if the number of connections is above <n>. /@PCO<n> Generate an alert to the fault manager if the peak number of connections is above <n>. /@PSU Generate an alert to the fault manager if the peak percentage of server utilization is above percent. NSVWATCH collects statistics about the CPU activity of a Novell NetWare Server. The data is collected on an interval basis and monitored for exceptions to user-specified thresholds. NSVWATCH accepts the following input parameters. Note that the < and > in the help information indicate user-supplied data and are not entered as part of the parameter. Parameters: o /iiterations - the number of times to poll the NetWare file server for statistical information o /smin - the time in minutes between each poll. o /d - display the output at the NetWare Server console. o /r[internetaddress] - send the output to the managing system with database. Internetaddress is optional but, if used, is the internetwork address of the managing system with database. If internetaddress is not used, the data is sent to the database machine specified in the bindery. o /@srup - monitor the server utilization (the number of times the file server`s polling process has executed); if the percentage of server utilization exceeds the value specified for threshold n, generate a generic alert. n is a percentage, and is a number between 1 and 100. The alert generated is NSV0006I. o /@fion - monitor the number of times the server has processed an Open File request for a client; if the number of Open File requests exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0007I. o /@ficn - monitor the number of times the server has processed a Create File request for a client; if the number of Create File requests exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0008I. o /@firn - monitor the number of times the server has processed a Rename Directory Entry request for a client; if the number of Rename Directory Entry requests exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0009I. o /@fidn - monitor the number of times the server has processed a Delete File request for a client; if the number of Delete File requests exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0010I. o /@disn - monitor the number of times the server has processed a Directory Search request for a client; if the number of Directory Search requests exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0011I. o /@fren - monitor the number of times the server has processed a Read File request for a client; if the number of Read File requests exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0012I. o /@fwin - monitor the number of times the server has processed a Write File request for a client; if the number of Write File requests exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0013I. o /@fbrn - monitor the number of bytes the server has read while processing Read File requests for clients; if the number of bytes read exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0014I. o /@fbwn - monitor the number of bytes the server has written while processing Write File requests for clients; if the number of bytes written exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0015I. o /@fsdn - monitor the number of File Attribute Table (FAT) sectors that the operating system needs to write to disk but has not yet written; if the number of not-yet-written FAT sectors exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0016I. o /@fswn - monitor the number of FAT sectors the NetWare operating system has written to disk since the operating system was loaded; if the number of FAT sectors written exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0017I. o /@pkrn - monitor the number of packets that the NetWare Link Support Layer (LSL) has received from all the underlying LAN drivers since the NetWare operating system was loaded; if the number of packets received exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0018I. o /@pktn - monitor the number of packets that the LSL has transmitted to the underlying LAN drivers since the NetWare operating system was loaded; if the number of packets sent exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0019I. o /@byrn - monitor the number of bytes that the LSL has received in all the packets from the underlying LAN drivers since the NetWare operating system was loaded; if the number of bytes received exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0020I. o /@bytn - monitor the number of bytes in all the packets that the LSL has transmitted to the underlying LAN drivers since the NetWare operating system was loaded; if the number of bytes sent exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0021I. o /@prtn - monitor the number of packets that the IPX module has routed from one network to another since the NetWare operating system was loaded; if the number of packets routed exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0022I. o /@rlon - monitor the number of times the server has processed a Log Record request for a client; if the number of Log Record requests exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0023I. o /@tran - monitor the number of times the server has performed a transaction on a file or group of files; if the number of transactions performed exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0024I. o /@conn - monitor the number of connections the server has with clients; if the number of connections exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0025I. o /@pcon - monitor the number of connections the server has with clients; if the peak number of connections exceeds the value specified for threshold n, generate a generic alert. The alert generated is NSV0026I. o /@psup - monitor the percentage of server CPU utilization; if the peak percentage of utilization during the polling interval exceeds the value specified for threshold n, generate a generic alert. n is a percentage, and is a number between 1 and 100. The alert generated is NSV0027I. ΓòÉΓòÉΓòÉ 10.3. Fault Management (NetWare Server) ΓòÉΓòÉΓòÉ For a full description of LMU/2 fault management implementation and capabilities, see the topics on fault management in the section on Management Applications (OS/2) in this document. Concepts specific to Novell NetWare Server are: o The fault reporter function is built into the LMU/2 NLM applications (VOLWATCH, NSVWATCH, and so forth); the applications themselves generate and forward alerts to the fault manager. AUEPITCH is not used on a Novell NetWare Server. o The name (internetwork address) of the fault manager must be specified in the bindery. See Customizing a Novell NetWare Server and LMULOAD for details. o The ability to generate generic alerts from user-written programs and forward them to the fault manager is not present in the Novell NetWare Server (there is no AUEDOSAL equivalent for the Novell NetWare Server). ΓòÉΓòÉΓòÉ 10.4. Terminate (NetWare Server) ΓòÉΓòÉΓòÉ Use SHUTDOWN to terminate all functions in a NetWare Server and, optionally, to restart the station. ΓòÉΓòÉΓòÉ 10.4.1. SHUTDOWN.NLM ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇ LOAD [volume:path] SHUTDOWN [/B[min] ] ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ SHUTDOWN.NLM Command Syntax SHUTDOWN.NLM operates much like its OS/2 counterpart: it shuts down the NetWare Server and optionally re-IPLs the computer. The /b option tells the NetWare Server station to re-IPL after shutting down. The number following the /b is the time in minutes to wait after shutting down, before re-IPLing. If no number follows the /b, the station re-IPLs immediately after shutting down. A /b15, for instance, tells the station to re-IPL 15 minutes after shutting down. Shutdown is initiated by an LMUCMD command from an administrator workstation or by entering the SHUTDOWN command through the NetWare Server system console. See the explanation in SHUTDOWN.EXE for more information. ΓòÉΓòÉΓòÉ 11. Will It Run In My Station? ΓòÉΓòÉΓòÉ The following table identifies which applications run in which network stations. --------------------------------------------------------------- | O P E R A T I N G S Y S T E M | |----------------------------------------------- LMU/2 | OS/2 | DOS | Novell | |----------------|-----------------| NetWare | Application | NetWare | IBM | NetWare | IBM | File | | Req. | Req. | Req. | Req. | Server | --------------------------------------------------------------- APPWATCH | x x | | | DOSVIRGA | | x x | | IPXWATCH | x | | | LMUGETCF | x x | | | NSVWATCH | | | x | NWRWATCH | x* | x | | OSRWATCH | x x | | | PERFCAP | x x | | | PERFWACH | x x | | | QDOSVPD | | x x | | QUERYVPD | x x | | | SHUTDOWN.EXE | x x | | | SHUTDOWN.NLM | | | x | SRVWATCH | x | | | VIRALERT | x x | | | VOLWATCH | | | x | --------------------------------------------------------------- * Only from within a DOS window under OS/2 2.0 ΓòÉΓòÉΓòÉ 12. LMU/2 Graphical User Interface ΓòÉΓòÉΓòÉ The LMU/2 Graphical User Interface (GUI) provides a visual representation of the workstations managed by LMU/2. The GUI allows you to quickly determine if a resource is in use and if it is functioning correctly. The GUI also allows you to select different views of the resources. o A resource is a workstation executing LMU/2 client programs, and is represented by a geometric shape, an icon, and text. o A view is a picture of a group of resources and of the graphical components used to describe them. The GUI can report the status of the network by the color and pattern of the resources in the views. As alerts are received for a given resource, its color and pattern change. These changes occur as long as the view is open even if the window is minimized. When a status change occurs, you are notified by a beep and by the flashing of the title bar of the window or the icon. You can also display a list of the alerts received by the individual resources. You can zoom in on specific areas of the view to concentrate on a set of resources or a region. You could also zoom in on a specific resource, minimize the view to an icon, and still observe that one resource while you use other applications. You can also selectively hide and show resources in order to highlight resources of special concern to you and specify the types of information to display about the resources. You might, for example, wish to see only the geometric shapes and, therefore, hide the text and icons. A background picture may be added to a view so that it is displayed behind the resources. The background picture can be any OS/2 metafile. After a picture is added to a view, you can continue to manipulate the resources in the view, but you cannot manipulate the picture in any way except to delete it. The GUI also provides an easy-to-use interface for submitting commands to the local workstation or to remote monitored workstations using LMUCMD.EXE. Besides prompting the user for the necessary LMUCMD parameters, this interface provides the ability to store complicated or lengthy command sequences. These stored command sequences can then be recalled using a descriptive user-defined alias. Using the GUI, the administrator can quickly identify which workstations have received alerts and issue the commands necessary to handle the various problems that arise. ΓòÉΓòÉΓòÉ 12.1. Overview ΓòÉΓòÉΓòÉ The GUI Workstation is the computer that is executing LMUGUI.EXE to monitor alerts, forwarded by the fault manager system, and to manage workstations. The GUI displays a graphical representation of all, or a subset, of the workstations in the LMU/2 LAN. Each workstation in this view is represented by a graphical symbol. The workstations are assigned symbols based on a combination of their LMU/2 function, operating system, and network software (for example, an LMU/2 managing system is represented by a star while an OS/2 LAN Requester is represented by a trapezoid). A view will contain some combination of collections and nodes based on one of the following view types: o Both nodes and collections o All nodes o All collections o All servers o All nodes belonging to a given collection A Collection is a managing system and a Node is a managed system. Each resource is displayed with one of four colors to indicate the status of its associated workstation. A node's status is determined by the alerts that it receives, or is directly set by the GUI user. A collection's status is determined by the alerts that are received by its managed systems, or is directly set by the GUI user. The color and status combinations are: COLOR STATUS -------------------------------------------------- Gray: Unknown Green: Active Red: Inactive Yellow: Threshold exceeded or user alert When a node receives an alert, its symbol is displayed with an overlaying pattern in addition to its possible color change. Once the user displays the node's alerts, this "new-alert" indicating pattern is automatically removed. This allows the user to quickly determine which nodes have received "unseen" alerts. The new-alert pattern is also placed on the symbol representing the node's managing system. This is particularly useful when the user has selected a view type in which the node receiving the alert is no longer being displayed but its collection is. When the new alerts for all of the nodes under a given collection have been viewed, the new-alert pattern will be removed from that collection. This pattern may be manually removed from any resource using the Change Status menu pull down. An icon and a text field are associated with each symbol. The text contains the computername of the node or collection. The icon, like the choice of symbol, is intended to provide the user with an additional visual representation of the type of workstation. The icons are (64x64 pixel) screen pointers, built in device-independent format using the OS/2 icon editor available with the OS/2 Toolkit. There is one icon file associated with each of the ten types of symbols. They are named LMUGUIx.ICO, where x is 0 thru 9, and can be found in the LMU/2 subdirectory. If you would rather use one or more of your own icons, simply copy the icon to a directory found in the CONFIG.SYS DPATH statement, and change its name to that of one of the ten supplied icons; it will be used by the GUI. ΓòÉΓòÉΓòÉ 12.2. Using The GUI ΓòÉΓòÉΓòÉ The GUI is invoked by entering LMUGUI on the OS/2 command line or by selecting the GUI from a program group or folder. At startup, the GUI queries the managing system indicated in the GUI workstation's LMU.INI file for a list of nodes that have sent in initial heartbeats. It then parses this list to determine which of the collection's nodes, based on the initial view type indicated in the .INI file, will be displayed. At any time after startup, the user can select another view type and the view will be redrawn showing the resources appropriate under the new view type. If a view is to display less than 20 resources, they will be shown in an elliptical pattern centered within the GUI's main, or view, window. If there are more than 20, they will be lined up in rows and columns beginning at the bottom left-hand corner of the view window. The height and width ratios indicated in the LMU.INI file will be used to determine the aspect ratio for the elliptical pattern. Controls The following actions are controlled by the mouse: o Button 1: Single click: Select resource Double click: Display Execute Commands window Click & hold: Mark a region with a rubber-band selection box; used for zooming on regions and positioning background pictures o Button 2: Single click: Not used Double click: Display the Display Alerts window for nodes and the Change Status window for collections Click & hold: Move resource Manipulating the View The user can dynamically change the type of resources displayed in the view by selecting Show Nodes, Show Servers, or Show Collections & Nodes from the menu bar. The user can also chose to limit the view to those nodes reporting to a given collection by first selecting the collection with mouse button 1 and then selecting Expand a Collection from the menu bar. The Refresh View function causes the view to be redrawn. During this process, the desired resources, based on view type, are reposition in an elliptical pattern centered in the view window. This process is very similar to the events performed at GUI startup. This function is particularly useful when several nodes have been added with the automatic Refresh option disabled. The user can zoom in on a specific area of the view to concentrate on a set of resources or a region by marking a resource or region using mouse button 1 and selecting Zoom in from the menu. Zoom out reverses this process, Zoom fit expands the marked region to fill the view window, and Undo zoom undoes the last zoom operation. As the area being viewed expands and contracts, the size of the symbols is adjusted to display as much information as possible. The size of the text and icons remains constant. Display labels is used to turn on and off the resources' icons and text fields. When the size of the text and icons versus the size of the symbols is extreme, the GUI stops displaying them. The user can turn them back on using Display labels. In a given view, the user can elect to hide and show certain resources. Selecting a resource with mouse button 1 and selecting Hide, causes the resource to become invisible. Selecting Show only causes all but the selected resource to become invisible. Show all causes all hidden resources to become visible. When alerts are received for resources that are not currently visible, any status changes are recorded but the user will not be notified by the customary beeps and flashing title bar. This includes resources that are hidden, outside the current zoom region, or not being displayed in the current view type. The user can reposition resources by clicking and holding down mouse button 2 on a resource and dragging it to a new location. The user may also select a resource using mouse button 1 and selecting Move from the menu. The resource can then be moved with the cursor keys or the mouse. Windows The user can submit commands to either local or remote workstations using the Execute Commands window. Additionally, the user can save commands in a file for future use. The Execute Commands window is invoked either by double clicking on a resource with mouse button 1 or by selecting a node and the Execute Commands menu item. The user can display the alerts received by a given node by selecting the node with mouse button 1 and selecting Display Alerts from the menu. This causes a list of alerts to be displayed. At this point, the user can delete the list of alerts and change the node's status. This function may also be invoked by simply double clicking mouse button 2 on a node. To change a node's status, use the Change Status window. Here the user is asked to select one of the four defined status values. This window is automatically displayed when the user requests that the alerts for a given node be deleted. It may also be invoked from the Display Alerts window or by selecting a node and selecting the Change Status menu item. At any time after GUI initialization, the user may chose to query additional managing systems for their lists of workstations that have sent in initial heartbeats. This function is invoked by selecting the Query Managing System item from the menu. The user is prompted for the name of the desired managing system and a query is sent. The user is not required to wait for the reply. When the reply arrives, the GUI automatically merges the new resources with the existing data and refreshes the view based on the currently selected view type. The user may submit multiple queries at a given time. Help The Legend window shows the icons and symbols assigned to the ten types of resources and the colors and patterns representing the different status values. Selecting help from the GUI results in a hypertext link to the online LMU/2 Users Guide. Background Pictures The GUI allows the user to add or remove background pictures. These pictures are OS/2 metafiles. A picture is added by selecting the Add background picture item from the menu. The user is asked to select, using the standard file dialog, a metafile from a list of all metafiles found on the system. Once this is done, the user can size the metafile in the same manner that an area is marked for a zoom function. The metafile is "dropped" onto the view by either clicking mouse button 1 inside the rubber band selection box or reselecting the Add background picture menu item. A picture can be deleted from a view using the Delete background picture menu item. ΓòÉΓòÉΓòÉ 12.3. Executing Commands from the LMU/2 GUI ΓòÉΓòÉΓòÉ The Execute Commands window is used to submit any OS/2 command line command to the GUI workstation or to remote workstations. Remote commands are executed via the LMUCMD function. Entry fields, check boxes, and other window items are used to enter the LMUCMD parameters. An OS/2 session is created for each submitted command. The GUI also maintains a list of Stored Command Sequences in a file. A Command Sequence consists of the desired OS/2 command line command, the command destination and output choices, and a descriptive name. The name of the file is specified in the LMU.INI file. When the Execute Commands window is opened, the contents of this file is loaded into memory and displayed in a list box. The user can select a command from this list and either submit it as is or make changes to it prior to submission. The user can add, delete, or modify command sequences in this list. The user can also choose to discard these changes or save them in the original file. ΓòÉΓòÉΓòÉ 12.4. Required Alert Table Entries ΓòÉΓòÉΓòÉ The GUI can receive alerts directly from the fault manager. This is accomplished by adding an automated response entry for each desired alert to the fault manager's alerts processing table. The automated response entry must specify LMUGUICM -$c "-$t in the command string. All managing systems that have been queried will automatically send heartbeat alerts for any new managed systems to the GUI; therefore, do not forward initial heartbeat alerts to the GUI using the alerts processing table. You must add an alerts table entry specifying the LMUGUICM string for the "Terminating heartbeat received" alert (LMU0903I) and for the "Heartbeat overdue" alert (LMU0904W). The following is an example of these required table entries: 5799PYA 02 2100 * localcpu 0000Y 00FFY 0 0 94 LMUGUICM -$c "-$t 5799PYA 01 2100 * localcpu 0000Y 00FFY 0 0 96 LMUGUICM -$c "-$t ΓòÉΓòÉΓòÉ 12.5. LMU/2 Control File GUI Parameters ΓòÉΓòÉΓòÉ Below is a portion of the sample LMU/2 control file. This sample identifies all the keywords used by the GUI. The values shown in this sample must be replaced with information specific to your network. ################################################################# # THE FOLLOWING PARAMETERS APPLY TO "FAULT MANAGER" SYSTEMS. # ################################################################# # Identifies the GUI workstation APP(LMU_UTILITY), KEY(GRAPHICAL_USER_INTERFACE), ASCIIZ(computername or internetwork address); ################################################################# # THE FOLLOWING PARAMETERS APPLY TO THE LMU/2 GRAPHICAL # # USER INTERFACE (GUI). # ################################################################# # Indicates the node and collection grouping to be # displayed at GUI startup. # # NOTE: The character value for this field must be specified as one # capital letter. For example: (A) to indicate all collections and nodes. # For additional information see the GUI documentation. APP(LMU_UTILITY), KEY(GUI_INITIAL_DISPLAY), ASCIIZ(char-1); # Indicates which symbol is associated with the ten types # of view objects. # # NOTE: The hexnum value for this field must be specified # as 20 hexadecimal digits. For example: (04030A0806020709050B). # For additional information see the GUI documentation. APP(LMU_UTILITY), KEY(GUI_NODE_SYMBOLS), HNUM(hexnum-20); # Indicates the text color and background color to be used # when commands are submitted via the GUI. # # Note: The character values for this field must be specified # as two 2-digit numbers separated by a comma. For example: (34,47) # to indicate white text on a black background. # For additional information see the GUI documentation. APP(LMU_UTILITY), KEY(GUI_COLORS), ASCIIZ(num_text,num_background); # Indicates the name and the nominal point size, in tenths, of the # image font used to display all text in the GUI window. # # Note: The character values for this field must be specified as a # character field and a 3-digit number, separated by a comma. # For example: (Helv,100) to indicate Helvetica 10 point. # For additional information see the GUI documentation. APP(LMU_UTILITY), KEY(GUI_FONTS), ASCIIZ(char_font_name,num_point_size); # Identifies the location of the file to contain # command sequences stored by the GUI. APP(LMU_UTILITY), KEY(GUI_COMMANDS_TABLE), ASCIIZ(path\filename); # Indicates which pattern is used to indicate that a node or # collection has received alerts. # # NOTE: The hexnum value for this field must be specified # as 2 hexadecimal digits. For example: (0C) to indicate medium # density, diagonal hash marks. # For additional information see the GUI documentation. APP(LMU_UTILITY), KEY(GUI_PATTERN), HNUM(hexnum-2); # Indicates if the view is to be refreshed when a node is added due # to the arrival of an alert for an unknown workstation. Coding # N or n indicates that an automatic refresh is not done. # # NOTE: The character value for this field must be specified as one # capital letter. For example: (N). # For additional information see the GUI documentation. APP(LMU_UTILITY), KEY(GUI_AUTO_REFRESH), ASCIIZ(character-1); # Indicates the height and width ratios that will be used as the # aspect ratio for the ellipse used to display the workstations. # # Note: The character values for this field must be specified as # two 3-digit numbers separated by a comma. For example: (480,640) to # indicate an ellipse that approximates the height-to-width ratio # of a standard monitor in 640 X 480 mode. # Note: specifying (001,001) will result in a circle. # For additional information see the GUI documentation. APP(LMU_UTILITY), KEY(GUI_COORDINATES) ASCIIZ(num_height,num_width); ΓòÉΓòÉΓòÉ 12.6. GUI Control File Variables ΓòÉΓòÉΓòÉ The LMU/2 variables for the GUI are defined using the keywords described below. These keywords are included in the sample LMU/2 control file (LMUCTL.SMP) shipped on the LMU/2 diskettes. These variables are used to determine the configuration and content of the GUI. o GRAPHICAL_USER_INTERFACE The computer name (OS/2 LAN Requester computername or NetWare Requester for OS/2 internetwork address) of the administrator workstation that is running the GUI. This keyword must be specified by any fault manager system that wishes to communicate with the GUI. o GUI_INITIAL_DISPLAY Indicates the node and collection grouping that is displayed at GUI startup. Note that the value must be entered as one capital letter. If this keyword is not specified, the default value is A. Value Description ----------------------------------- A All nodes and collections N Only nodes C Only collections S Only servers o GUI_NODE_SYMBOLS Indicates which symbol is associated with each of the ten types of view resources. Any symbol name ending with a "2" is identical to its like-named symbol except for the addition of an octagon in the bottom left-hand corner. Note that the value must be entered as hexadecimal, and must be twenty digits (10 pairs of digits, which map to the resources in the order listed below). Resource type --------------------- Unknown OS2 LAN Requester OS2 NETWARE Requester OS2 Interoperable* DOS LAN Requester DOS NetWare Requester DOS Interoperable* LAN Server NetWare Server Collection * "Interoperable" refers to a station running both IBM and NetWare requesters. These are the pairs of digits and the symbols they represent. hex # Symbol hex # Symbol ---------------------------- ---------------------------------- 01 Rectangle 0D Rectangle2 02 Triangle 0E Triangle2 03 Hexagon 0F Hexagon2 04 Circle 10 Circle2 05 Parallelogram 11 Parallelogram2 06 Pentagon 12 Pentagon2 07 Diamond 13 Diamond2 08 Square 14 Square2 09 Octagon 15 Octagon2 0A Trapezoid 16 Trapezoid2 0B Star 17 Star2 0C Star in a circle 18 Star in a circle 2 If this keyword is not specified, the default value is "04030A0806020709050B", which translates to: Resource type Symbol ----------------------------------------- Unknown Circle OS2 LAN Requester Hexagon OS2 NETWARE Requester Trapezoid OS2 Interoperable Square DOS LAN Requester Pentagon DOS NetWare Requester Triangle DOS Interoperable Diamond LAN Server Octagon NetWare Server Parallelogram Collection Star o GUI_COLORS Indicates the text and background colors of the OS/2 sessions that the GUI starts in order to submit commands. Note that the value must be entered as two hexadecimal numbers separated by a comma. Each value must be two digits. If this keyword is not specified, the default value is "34,47". hex # Color hex # Symbol ---------------------------- ---------------------------------- 30 Black Text 40 Black Background 31 Red Text 41 Red Background 32 Green Text 42 Green Background 33 Yellow Text 43 Yellow Background 34 Blue Text 44 Blue Background 35 Magenta Text 45 Magenta Background 36 Cyan Text 46 Cyan Background 37 White Text 47 White Background o GUI_FONTS Indicates the name and the nominal point size, in tenths, of the image font used to display all text in the GUI window. Note that the value must be entered as a character string and a 3-digit number separated by a comma. If this keyword is not specified, the default value is the system default font and point size. o GUI_COMMANDS_TABLE Identifies the path and name of the file to contain command sequences stored by the GUI. Note that the value must be entered as a character string. If this keyword is not specified, the default filename is LMUGUI.TAB located in the root directory of the boot drive. o GUI_PATTERN Indicates which pattern is used to indicate that a node has received alerts that have not been viewed by the GUI user. Note that the value must be entered as hexadecimal, and must be two digits. If this keyword is not specified, the default value is "0C". hex # Pattern hex # Pattern ---------------------------- ---------------------------------- 01 Dense pattern 1 09 Vertical lines 02 Dense pattern 2 0A Horizontal lines 03 Dense pattern 3 0B Diagonal hash marks 1 04 Dense pattern 4 0C Diagonal hash marks 2 05 Dense pattern 5 0D Diagonal hash marks 3 06 Dense pattern 6 0E Diagonal hash marks 4 07 Dense pattern 7 08 Dense pattern 8 o GUI_AUTO_REFRESH Identifies the events that occur when an alert is received for an unknown workstation. N Add new nodes side by side in the bottom left-hand corner of the view. Y Refresh the view each time a node is added. The view resources are redrawn so that the new node is included in the elliptical pattern that is centered in the view window. Note that the value must be entered as a capital letter, and must be one character. If this keyword is not specified, the default value is Y. o GUI_COORDINATES Indicates the height and width ratios used to determine the aspect ratio for the ellipse used to display the view resources. Note that the value must be entered as two decimal numbers separated by a comma. Each value must be three digits. If this keyword is not specified, the default value is "001,001" which results in a circle. ΓòÉΓòÉΓòÉ 13. LMU/2 Scheduling Services ΓòÉΓòÉΓòÉ The LMU/2 scheduling service (LMUSTEP) provides network administrators with the ability to schedule events in the network according to any of the following criteria: o Time of day (hour, minute) o Week of year o Day of week (Sunday, Monday, and so forth) o Month of year o Month and day o Month, day, and year o One time only o Every occurrence of the time/date specified. The scheduler can be used for any event that can be triggered by an OS/2 command issued from an LMU/2 administrator workstation or from a command string in the user-defined alerts table. These events include: o Scheduled execution of LMU/2 applications - Performance monitoring - Configuration monitoring o Automatic report generation o Log file maintenance o Backup and recovery o Secure backup of sensitive data o Device status monitoring o Scheduled execution of other OS/2 commands and applications Only one copy of LMUSTEP can be running in a single administrator workstation at any given time. There are four main components to the scheduler: The executable module LMUSTEP.EXE The group file A user-created ASCII file that identifies all the target workstations, divided into groups. The default name is SCHEDULE.GRP. The schedule file A user-created ascii file that contains the schedule of commands (events) to be triggered, one record per event. The default name is SCHEDULE.TIM. The LMUSTEP log file The file created by LMUSTEP that contains a record of each transaction (command) attempted using LMUSTEP. The default name is SCHEDULE.LOG. You must specify in the LMU/2 control file the name and location of the group file, the schedule file, and the log file, as well as the frequency with which the schedule file is to be checked for changes. The default frequency is 60 minutes (once an hour). An additional component, LMUSTEPU, is used in an alerts table entry to add an event to the schedule file. There are also four utilities that prune the LMUSTEP log file, the LMU/2 message log file, the schedule file, and the LMU/2 change log file. These utilities are discussed in Pruning the Files. ΓòÉΓòÉΓòÉ 13.1. Creating the Scheduler Files ΓòÉΓòÉΓòÉ The easiest way to create or update the schedule file or the scheduler group file is to use the scheduler graphical user interface (GUI). Schedule File If a group was created for LMU/2 on the Desktop (OS/2 1.3) or a folder was created (OS/2 2.0), start the Schedule File Editor by selecting it from the Desktop group or folder. If no group or folder was created, start the Schedule File Editor by entering the command LMUSCHED from the OS/2 command line at the administrator workstation. The Schedule File Editor shows the entire schedule file, a few lines at a time, and provides fields to select from to create new schedule lines or change existing ones. If the schedule file GUI has not been installed, you can create or update the schedule file (with somewhat more difficulty) using a text editor. The format of the schedule file is described in The Schedule. You can also add entries to the schedule file dynamically as a result of alert conditions. See LMUSTEPU for details. Group File If a group was created for LMU/2 on the Desktop (OS/2 1.3) or a folder was created (OS/2 2.0), start the Group File Editor by selecting it from the Desktop group or folder. If no group or folder was created, start the Group File Editor by entering the command LMUGROUP from the OS/2 command line at the administrator workstation. If the group file GUI has not been installed, you can create or update the group file (with somewhat more difficulty) using a text editor. The format of the group file is described in The Group List. ΓòÉΓòÉΓòÉ 13.1.1. The Group List ΓòÉΓòÉΓòÉ The group list consists of one record, or line, per workstation, and identifies the group or groups to which the workstation belongs. The user decides the group names, what the groups should represent, and which workstations belong in which groups. A group could be all the servers, or all the workstations in a particular building, or all the workstations in a particular department, for example. Format: o Workstation ID - 1-95 characters, beginning in column 1. For an IBM OS/2 LAN Requester, it is the computer name specified in the IBMLAN.INI file in the workstation; for a Novell NetWare Requester for OS/2, it is the internetwork address of the workstation. o space o Groups - One or more group names (1-8 characters each), separated by a space, that identify the groups to which this workstation belongs. A workstation could be in a building group, a function group (records retention), and an operating-system-specific group (OS/2 2.0 users), for example. Group names are not case-sensitive: PYRL06 and Pyrl06 are interpreted as the same group. The maximum record (line) length is 256. Γöé- Column 1 V |- Blank-| V V wkstation grpname1 grpname2 Example: srv1dmn group2 servers RQSTR1 GRoup1 RQSTR2 GROUP1 group2 RQSTR3 group1 RQSTR4 group2 ALSMACH group2 srv2dmn servers srv3dmn servers In this example, there are three workstations in the group called "servers", three in the group called "group1", and four in the group called "group2". ΓòÉΓòÉΓòÉ 13.1.2. The Schedule ΓòÉΓòÉΓòÉ The schedule file consists of one record, or line, for each event. Each line begins with seven date-time fields, separated from each other by one or more spaces, followed by an action target field, an action control field, and the complete command to be executed. The command is usually an LMUCMD command to direct an action at a remote workstation. An asterisk in place of any of the date-time parameters indicates "any" or "regardless of". Format: o Date-time - Hour - In 24-hour time (6 = 6 a.m., 13 = 1 p.m.) - space - Minute - 0-59 (minutes after the hour) - space - nth week - First, second, third, fourth, 1, 2, 3, 4 - space - Day of week - Spelled out, first three letters, or a number: Monday, Mon, 1, Tuesday, Tue, 2, and so forth. - space - Month - Spelled out, first three letters, or a number: January, Jan, 1, February, Feb, 2, and so forth. - space - Day of month - 1-31 - space - Year - Full year (1991, 1992, and so forth) - space o Action target - Identifies the workstation or group of workstations on which the command is to be executed. One of the following: - /ggroupname - The command is to be executed on a group of workstations. Groupname is required, and is a group name defined in the group file. - /uworkstation - The command is to be executed on a single workstation. Workstation is required: for an IBM OS/2 LAN Requester, it is the computer name specified in the IBMLAN.INI file in the workstation; for a Novell NetWare Requester for OS/2, it is the internetwork address of the workstation. - /a - The command is to be executed on every workstation listed in the group file. - Blank (space) - The command is to be executed only on the administrator workstation that is running LMUSTEP. o Action control - Qualifies how the command is executed and how the results are logged. This section does not apply when the Action Target is blank. - /q - The command is to be executed on the target workstations without waiting for output. - /r time - The time, in seconds, the command will wait before terminating the request. Range is 1-120 seconds; use 0 to wait forever. - /f[c] time filename - Place the output of the action, and a copy of the command that was executed, in the file specified by filename. If c is specified, clear the file before placing the new data. Time functions the same as in the /r option. - /l[c] time filename - Same as /f, except do not place a copy of the command in the file. o Command - Full specification, with parameters. Any command that can be entered from an OS/2 command line. Examples: 10 25 * Monday * * * c:\tools\virscan d: * 0 * * * * * /g group1 queryvpd /r * 0,15,30,45 * friday * * * /a copy c:audit.log c:audit.bak 9 30 * 2,4 10 * 1991 /u MACHINE1 /f c:jerry.dir dir c:*.sss 8 30 * monday,friday * * * /g group2 type c:\cmlib\acslan.log 2 0 fourth sunday october * * /a timer Fall Backward 0 15 * * * * * prunestp # 30 0 20 * * * * * prunelmu # 30 0 25 * * * * * prunechg# 30 14 25 * * * * * prunetim The first example, for instance, specifies: At 10:25 a.m. every Monday run the VIRSCAN program located on the C: drive of this workstation (the administrator workstation) against the D: drive . The fourth example specifies: At 9:30 a.m. every Tuesday and Thursday in October of 1991, execute the DIR command for *.sss files on the C: drive of the workstation whose computername is MACHINE1, and put a copy of the command and the output into a file named jerry.dir. The sixth example specifies: At 2:00 a.m/ the fourth Sunday of every October, execute the locally-written program called TIMER on all workstations listed in the group file. Fall and Backward are parameters to TIMER, and (in this example) serve to set the system clock back one hour to account for daylight savings time. In this example, TIMER is assumed to reside on all workstations. ΓòÉΓòÉΓòÉ 13.1.3. LMUSTEPU.EXE ΓòÉΓòÉΓòÉ LMUSTEPU is a command to be placed in the command string of an entry in the user-defined alerts table. Its purpose is to add an entry to the schedule file when the chosen alert condition occurs, to cause some action (usually remedial) to take place at a particular time. For example: in the alert table entry for a user-generated alert for a "full log file" condition, the LMUSTEP command could specify a schedule file entry to trigger pruning the log file. The format for LMUSTEPU is: LMUSTEPU schedule-file-entry-information The entry to be added to the schedule file is generally for a one-time occurrence, and usually of an event not already scheduled. The entry to be added does not affect already-scheduled events, and does not alter any existing schedule file entries. ΓòÉΓòÉΓòÉ 13.2. Running the Scheduler ΓòÉΓòÉΓòÉ If a group was created for LMU/2 on the Desktop (OS/2 1.3) or a folder was created (OS/2 2.0), start the LMU/2 scheduler by selecting it from the Desktop group or folder. If no group or folder was created, start the scheduler by entering the command LMUSTEP from the OS/2 command line at the administrator workstation. ΓòÉΓòÉΓòÉ 13.2.1. LMUSTEP.EXE ΓòÉΓòÉΓòÉ LMUSTEP.EXE initiates scheduled events at target workstations based on the contents of the LMU/2 Schedule File and LMU/2 Group File. LMUSTEP runs on an administrator workstation only, and should be executed automatically (through an entry in the STARTUP.CMD file or the CONFIG.SYS file) every time the administrator workstation is started. ΓòÉΓòÉΓòÉ 13.2.2. The Scheduler Log ΓòÉΓòÉΓòÉ The LMU scheduler log file contains a record of all transactions that were attempted through the scheduler. The name and location of the log file are identified in the LMU.INI file. Each entry in the log contains a time/date stamp, a copy of the command executed, parameters such as target workstation, execution parameters and a return code. The scheduler log file should be pruned periodically to maintain manageability. Example: date time command return code -10/18/91 00:15:00 prunestp # 30 -10/18/91 00:20:00 prunelmu # 30 -10/18/91 00:25:00 prunechg # 30 -10/18/91 00:25:13 prunetim -10/18/91 01:00:00 queryvpd /r -10/18/91 01:00:22 /R┬álmucmd /T45 RQSTR1 queryvpd /r rc = timeout -10/18/91 01:01:23 /R┬álmucmd /T45 RQSTR3 queryvpd /r rc = timeout -10/18/91 01:02:22 /R┬álmucmd /T45 MACHINE1 queryvpd /r rc = timeout -10/28/91 13:00:00 queryvpd /r -10/28/91 13:00:21 /R┬álmucmd /T45 RQSTR1 queryvpd /r rc = 0 -10/28/91 13:01:00 /R┬álmucmd /T45 RQSTR3 queryvpd /r rc = 0 -10/28/91 13:01:38 /R┬álmucmd /T45 MACHINE1 queryvpd /r rc = 0 -10/28/91 13:49:00 /Q┬álmucmd /Q RQSTR3 LP3820 W:\CARRESUM.LIS -10/28/91 13:57:00 /Q┬álmucmd /Q RQSTR3 LP3820 W:\CARRESUM.LIST -10/28/91 14:00:00 queryvpd /r -10/28/91 14:00:20 /R┬álmucmd /T45 RQSTR1 queryvpd /r rc = 0 -10/28/91 14:00:59 /R┬álmucmd /T45 RQSTR3 queryvpd /r rc = 0 -10/28/91 14:01:37 /R┬álmucmd /T45 MACHINE1 queryvpd /r rc = 0 -10/28/91 15:00:00 queryvpd /r -10/28/91 15:00:22 /R┬álmucmd /T45 RQSTR1 queryvpd /r rc = 0 -10/28/91 15:01:03 /R┬álmucmd /T45 RQSTR3 queryvpd /r rc = 0 -10/28/91 15:01:42 /R┬álmucmd /T45 MACHINE1 queryvpd /r rc = 0 -10/28/91 16:00:00 queryvpd /r -10/28/91 16:00:23 /R┬álmucmd /T45 RQSTR1 queryvpd /r rc = timeout -10/28/91 16:01:23 /R┬álmucmd /T45 RQSTR3 queryvpd /r rc = 0 -10/28/91 16:02:00 /R┬álmucmd /T45 MACHINE1 queryvpd /r rc = 0 -10/28/91 17:00:00 queryvpd /r -10/28/91 17:00:23 /R┬álmucmd /T45 RQSTR1 queryvpd /r rc = timeout -10/28/91 17:01:24 /R┬álmucmd /T45 RQSTR3 queryvpd /r rc = 0 -10/28/91 17:02:04 /R┬álmucmd /T45 MACHINE1 queryvpd /r rc = 0 -10/28/91 18:00:01 queryvpd /r -10/28/91 18:00:23 /R┬álmucmd /T45 RQSTR1 queryvpd /r rc = timeout -10/28/91 18:01:24 /R┬álmucmd /T45 RQSTR3 queryvpd /r rc = timeout -10/28/91 18:02:23 /R┬álmucmd /T45 MACHINE1 queryvpd /r rc = timeout -10/28/91 19:00:00 queryvpd /r -10/28/91 19:00:22 /R┬álmucmd /T45 RQSTR1 queryvpd /r rc = timeout -10/28/91 19:01:24 /R┬álmucmd /T45 RQSTR3 queryvpd /r rc = timeout -10/28/91 19:02:23 /R┬álmucmd /T45 MACHINE1 queryvpd /r rc = timeout In this example, an event in the schedule file specified sending the QUERYVPD command once an hour to the workstations in GROUP1 (RQSTR1, RQSTR3, and MACHINE1), beginning at 1:00 a.m. on Oct 28, 1991. If the workstation was logged on when each QUERYVPD command was triggered, the output was routed back to the data base and a return code of 0 was returned. If the workstation did not respond in 45 seconds (T45), the request was cancelled and the return code was set to 'timeout'. All workstations were active at 1:00 a.m. (13:00), 2:00 a.m. (14:00) and 3:00 a.m. (15:00) but RQSTR1 was inactive at 16:00 and later, and workstations RQSTR3 and MACHINE1 were not active at 18:00 or later. ΓòÉΓòÉΓòÉ 14. Pruning the Files ΓòÉΓòÉΓòÉ LMU/2 provides several utilities to prune files. Use: PRUNELMU to prune the LMU/2 message log. PRUNECHG to prune the LMU/2 change log. PRUNESTP to prune the LMU/2 scheduler log. PRUNETIM to prune the LMU/2 schedule file. ΓòÉΓòÉΓòÉ 14.1. Pruning the LMU/2 Message Log ΓòÉΓòÉΓòÉ The PRUNELMU command prunes the LMU/2 message log based on parameters you specify. The syntax of the PRUNELMU command is: PRUNELMU parameter Parameters: o # days (poundsign days) - Number of days for which entries are to be retained, beginning with today and counting back. A value of 4, for example, will cause this utility to remove all entries except those for today's date and the three preceding days. o d date - Cutoff date. Format is mm/dd/yy. Delete all entries in the log that have a date older than this date. o s size - Maximum number of lines to leave in the log. Lines are deleted from oldest entry to newest until this size is reached. o r returncode - Delete all entries that contain this LMU/2 return code. The return code must be specified as 8 contiguous characters; alphabetic characters can be specified as either upper or lower case. ΓòÉΓòÉΓòÉ 14.2. Pruning the LMU/2 Change Log ΓòÉΓòÉΓòÉ The PRUNECHG command prunes the LMU/2 message log based on parameters you specify. The syntax of the PRUNECHG command is: PRUNECHG parameter Parameters: o # days - Number of days for which entries are to be retained, beginning with today and counting back. A value of 4, for example, will cause this utility to remove all entries except those for today's date and the three preceding days. o d date - Cutoff date. Format is mm/dd/yy. Delete all entries in the log that have a date older than this date. o s size - Maximum number of lines to leave in the log. Lines are deleted from oldest entry to newest until this size is reached. ΓòÉΓòÉΓòÉ 14.3. Pruning the LMU/2 Scheduler Log ΓòÉΓòÉΓòÉ The PRUNESTP command prunes the LMU/2 message log based on parameters you specify. The syntax of the PRUNESTP command is: PRUNESTP parameter Parameters: o # days - Number of days for which entries are to be retained, beginning with today and counting back. A value of 4, for example, will cause this utility to remove all entries except those for today's date and the three preceding days. o d date - Cutoff date. Format is mm/dd/yy. Delete all entries in the log that have a date older than this date. o s size - Maximum number of lines to leave in the log. Lines are deleted from oldest entry to newest until this size is reached. o r returncode - Delete all entries that contain this LMU/2 return code. The return code must be specified as 1 character: - S - Successful commands - F - Failed commands - N - Commands with no return code ΓòÉΓòÉΓòÉ 14.4. Pruning the LMU/2 Schedule File ΓòÉΓòÉΓòÉ The PRUNETIM command prunes the LMU/2 message log of all outdated events, based on the current system date. The syntax of the PRUNETIM command is: PRUNETIM Note that PRUNETIM has no parameters. ΓòÉΓòÉΓòÉ 15. LMU/2 Profile Services ΓòÉΓòÉΓòÉ The OS/2 .INI files are in a special format that is not viewable with an ordinary text editor. The LMU/2 supplies programs that allow you to: o View the contents of OS2SYS.INI, OS2.INI, or any other existing .INI file o Update the contents of OS2SYS.INI, OS2.INI, or any other existing .INI file o Create a new .INI file. Viewing .INI Files To view the contents of a .INI file: o Use the DPRG and DINI programs to "dump" the contents of the .INI file into text files. The text files will contain statements describing the group, program, and user information. These statements are described in topic Control File for DPRG, DINI, LINI. Note: The concept of "group" does not apply to the OS/2 2.0 .INI files, unless you migrated from OS/2 1.3 to OS/2 2.0. Also, some OS/2 2.0 .INI contents can not be interpreted by the DPRG or DINI programs, and are presented as binary strings of data. Updating .INI Files To update the contents of one or more .INI files: 1. Use the DPRG and DINI programs to "dump" the contents of the .INI file into text files. 2. Use a text editor and the statements described in topic Control File for DPRG, DINI, LINI to: o Change information in the text files o Add your own information to the text files. The line length of some of the data can be up to 8 KB (approximately). Make sure that your editor supports this record length, or use the OS/2 System Editor to make the changes. You can combine the text files into one file, if desired; statements for more than one .INI file can be in the same text file. 3. Use the LINI program to rebuild the .INI file from your updated text file or files. The LINI program accepts as input only one text file at a time. Using multiple text files means multiple invocations of the LINI program. Creating .INI Files To create one or more .INI files: 1. Use a text editor and the statements described in topic Control File for DPRG, DINI, LINI to create a text data file containing the information you want in the .INI file or files. Statements for more than one .INI file can be in the same text file. The line length of some of the data can be up to 8 KB (approximately). Make sure that your editor supports this record length, or use the OS/2 System Editor to create the text file. 2. Use the LINI program to build the .INI file or files from your text file. ΓòÉΓòÉΓòÉ 15.1. DPRG ΓòÉΓòÉΓòÉ Syntax: ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ DPRG ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /U ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ inifile ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ datafile ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ /u - Indicates USER profile (OS2.INI) is to be dumped. inifile - File name of profile file to be dumped. datafile - File name where profile program information is to be dumped. DPRG Command Line Help Information /u Use the OS/2 USER profile (OS2.INI). inifile Filename of the binary .INI file to use. datafile Name of the file into which the .INI file data will be placed. Note: If you run both DPRG and DINI, be sure to specify separate output files for each. Use DPRG to convert the Desktop Manager Program and Group information from a user profile, such as OS2.INI, to a text file of commands. The file can then be modified with a text editor such as the OS/2 System Editor. Note: The concept of "group" does not apply to the OS/2 2.0 .INI files, unless you migrated from OS/2 1.3 to OS/2 2.0. Also, some OS/2 2.0 .INI contents can not be interpreted by the DPRG or DINI programs, and are presented as binary strings of data. DPRG adds punctuation (commas and semicolons) and indentations in the resulting text data file for readability. ΓòÉΓòÉΓòÉ 15.2. DINI ΓòÉΓòÉΓòÉ Syntax: ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ DINI ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /U ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /S ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ /B ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ inifile ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ datafile ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ /u - Indicates USER profile (OS2.INI) is to be dumped /s - Indicates SYSTEM profile (OS2SYS.INI) is to be dumped /b - Both SYSTEM and USER files are to be dumped. inifile - File name of profile file to be dumped. datafile - File name where profile information is to be dumped. DINI Command Line Help Information /u Use the OS/2 USER profile (OS2.INI). /s Use the OS/2 SYSTEM profile (OS2SYS.INI). /b Use both the OS/2 USER profile (OS2.INI) and the OS/2 SYSTEM profile (OS2SYS.INI). inifile File name of the binary .INI file to use. datafile Name of the file into which the .INI file data will be placed. Note: If you run both DPRG and DINI, be sure to specify separate output files for each. Use DINI to convert the run-time information for a program from a user profile (such as OS2.INI), from the system profile (OS2SYS.INI), or from any other named profile, to a text file of commands. The file can then be modified with a text editor such as the OS/2 System Editor. DINI adds punctuation (commas and semicolons) and indentations in the resulting text data file for readability. ΓòÉΓòÉΓòÉ 15.3. LINI ΓòÉΓòÉΓòÉ Syntax: ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LINI ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓööΓöÇΓöÇ drive ΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇ path ΓöÇΓöÇΓöÿ ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ datafile ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ datafile - name of file containing INI update information. LINI Command Line Help Information datafile Name of the file from which the target .INI file will be built or updated. The commands in the datafile identify which .INI file to use. Use LINI to convert a control file (a text file of commands, such as produced by DPRG or DINI and then modified) to a .INI file. LINI can be used to update OS2SYS.INI, OS2.INI, or any other true .INI file, or to create a new .INI file. o If LINI does not find an existing .INI file by the name specified in the control file, LINI creates the .INI file; otherwise LINI updates the existing file. o If the group, program, profile, and keywords in the control file are not in the .INI file, LINI adds the information from the control file; otherwise, LINI replaces the corresponding information in the .INI file with the values from the control file; Note: The concept of "group" does not apply to the OS/2 2.0 .INI files, unless you migrated from OS/2 1.3 to OS/2 2.0. LINI is used with the customized LMU/2 control file to set the necessary program variables and options in each computer to run the LMU/2 programs. (See the discussion of the LMU/2 control file and LMU.INI file in LMU.INI File.) LINI ignores any comments, punctuation, or indentation in the input text data file. They are not stored in the resulting .INI file. ΓòÉΓòÉΓòÉ 15.4. Control File for DPRG, DINI, LINI ΓòÉΓòÉΓòÉ The control file is a text data file that contains a series of groups of statements. Each group of statements defines the operation that is to be performed when building or updating the .INI file. Each group of statements begins with one of the following DEFINE or DELETE statements: DEFINE_GROUP* DEFINE_PROGRAM* DEFINE_PROFILE DELETE_PROGRAM * DELETE_PROFILE * Not applicable to OS/2 2.0 .INI files unless migrated from OS/2 1.3. The statements are processed sequentially, in the order they are encountered in the file. Multiple DEFINE_GROUP statements can be issued for the same group, for instance, to set and reset the PROTECTED attribute as needed (to allow updating a protected group). Multiple .INI files can be updated with a single text file. Statement Formats In the syntax definitions, the variable filename identifies the .INI file to be updated. The keywords SYSTEM and USER are mapped to the current system and user .INI files; these files are normally OS2SYS.INI and OS2.INI, respectively, but may be redefined by system calls. If the first non-blank character of a line is the character "#", that line is treated as a comment line. Select one of the following items to see the syntax definition for that statement. o DEFINE_GROUP o DEFINE_PROGRAM o DEFINE_PROFILE o DELETE_GROUP o DELETE_PROGRAM ΓòÉΓòÉΓòÉ 15.4.1. DEFINE_GROUP ΓòÉΓòÉΓòÉ Note: The concept of "group" does not apply to the OS/2 2.0 .INI files, unless you migrated from OS/2 1.3 to OS/2 2.0. DEFINE_GROUP is used to create or update an OS/2 1.3 Desktop Manager group. It does not apply to OS/2 2.0 unless you migrated from OS/2 1.3. DEFINE_GROUP INI_FILE(SYSTEM|USER|filename) TITLE(groupname) [VISIBILITY([VISIBLE|INVISIBLE]+ [PROTECTED|UNPROTECTED])] SYSTEM The OS2SYS.INI file is to be updated or was the source for the text data file. USER The OS2.INI file is to be updated or was the source for the text data file. filename The path and filename of the .INI file, other than OS2SYS.INI or OS2.INI, to be created or updated or from which the text data file was created. groupname The name to be used for the group. This name is referenced by the DEFINE_PROGRAM and DELETE_PROGRAM statements. VISIBLE Display the group in the Desktop Manager Group List. INVISIBLE Do not display the group in the Desktop Manager Group List. PROTECTED Do not permit programs to be added to or deleted from the group, or change the other group attributes in any way. PROTECTED is also known as "locked". UNPROTECTED Permit programs to be added to or deleted from the group; permit changes to the group attributes. Note that the keywords for VISIBILITY are joined by a plus, and may be in any order. See the example below. The following example defines a group named ONLAN, for use in the OS2.INI file. DEFINE_GROUP INI_FILE(USER) TITLE(ONLAN) VISIBILITY(VISIBLE+UNPROTECTED) Defining a group is not absolutely necessary. If the LINI program finds a DEFINE_PROGRAM statement for a non-existent group, the LINI program creates the group with the attributes VISIBILITY(VISIBLE+UNPROTECTED). This can be useful when creating a PROTECTED group. For example: o To create a PROTECTED group, omit the DEFINE_GROUP statement and let it default to an UNPROTECTED group definition (or issue the DEFINE_GROUP statement, defining the group as UNPROTECTED). Give the DEFINE_PROGRAM and DEFINE_PROFILE statements for the group. After the last statement for that group, issue a DEFINE_GROUP for the group, redefining it to be PROTECTED. o To update a PROTECTED group, first specify a DEFINE_GROUP for the group, defining it to be UNPROTECTED. Give the DEFINE_PROGRAM and DEFINE_PROFILE statements for the group. After the last statement for the group, issue another DEFINE_GROUP for the group, defining it to be PROTECTED. The DEFINE_GROUP for an UNPROTECTED group can appear anywhere in the file. ΓòÉΓòÉΓòÉ 15.4.2. DEFINE_PROGRAM ΓòÉΓòÉΓòÉ DEFINE_PROGRAM is used to add a new program to an OS/2 1.3 Desktop Manager group or to change the data associated with an existing program in a group. It does not apply to an OS/2 2.0 .INI file, unless you migrated from OS/2 1.3 to OS/2 2.0. DEFINE_PROGRAM INI_FILE(SYSTEM|USER|filename) GROUP(groupname) TITLE(programname) [TYPE([DEFAULT|FULLSCREEN|VIOWINDOW|PM|REAL|DLL])] [VISIBILITY([VISIBLE|INVISIBLE] [EXE(drive:\path\programname)] [PARAMS(parameters)] [WORK_DIR(drive:\path)] [ICON_FILE(drive:\path\iconame)] [ENV(environment-variable=setting)] [WINSTATE([INVISIBLE|MAXIMIZED|MINIMIZED|NOAUTOCLOSE |NORMAL])] [XY_SIZE(x,y,cx,cy)] SYSTEM The OS2SYS.INI file is to be updated or was the source for the text data file. USER The OS2.INI file is to be updated or was the source for the text data file. filename The path and filename of the .INI file, other than OS2SYS.INI or OS2.INI, to be created or updated or from which the text data file was created. groupname The name used for the group on the Desktop Manager Group List. TYPE Program type. break=fit. DEFAULT Default application. FULLSCREEN Full-screen application. VIOWINDOW Text-windowed application. PM Presentation Manager application. REAL PC DOS executable process. DLL Data Link Library member. VISIBILITY Whether to display in the Desktop Manager Program List for the group. break=fit. VISIBLE Display the group in the Program List. INVISIBLE Do not display the group in the Program List. EXE The drive, path, and name that specifies the executable program. PARAMS The parameters passed to the program when it is started. WORK_DIR The directory that will serve as the current directory for the program. It is the first directory in which the running program looks for its files, and is the directory in which the program stores any temporary files and output. The default is a null value. ICON_FILE The drive, path, and name that specifies the icon file for the program. The default is a null value. ENV A single environment variable for the program. This keyword can be repeated to specify more than one variable. Example: . . . ICON_FILE() ENV(prompt=$i[$p]) ENV(path=c:\os2;c:\muglib;c:\cmlib;c:\mylib) ENV(dpath=c:\os2;c:\muglib;c:\cmlib;c:\mylib) WINSTATE(NORMAL) . . . Note: To use this keyword, you must have applied corrective service diskette (CSD) 5015 or later. WINSTATE The window state when initially presented. break=fit. INVISIBLE Do not display the window. MAXIMIZED Present a maximized (full-size) window. MINIMIZED Present a minimized (iconized) window. NOAUTOCLOSE Do not close the window when the program terminates. NORMAL Visible, neither minimized nor maximized; close the window when the program terminates. XY_SIZE Window position coordinates. break=fit. x,y Coordinates for the lower left corner of the presentation space. cx Width of the presentation space. cy Height of the presentation space. ΓòÉΓòÉΓòÉ 15.4.3. DEFINE_PROFILE ΓòÉΓòÉΓòÉ DEFINE_PROFILE is used to add or change application-dependent information in a .INI file. This statement causes the LINI program to store data in a .INI file for any reason. By using the appropriate API macros, application programs can access the data as needed (see the Profile Function Calls in the Presentation Manager Programming Reference, Volume I of the IBM Operating System/2 Programming Tools and Information Version 1.3 ("the Toolkit"). The LAN Management Utilities/2 programs, for example, use information placed in the workstation LMU.INI files to identify such items as: o The identity of the managing station o The identity of the LMU/2 database station o The identity of the fault manager station o The location of the fault management user-written alerts table o The location of the LMU/2 database BIND statements o The location of the LMU/2 message log o The location of the LMU/2 change log o The LMU/2 pulse rate ("heartbeat" rate) o The threshold specifications for the performance commands. This information is placed in the LMU.INI file by the LINI program when it reads the DEFINE_PROFILE statements in the LMU/2 control file. See the example statements in topic Sample LMU/2 Control File. DEFINE_PROFILE INI_FILE(SYSTEM|USER|filename) APP(applicationname) [KEY(dataname)] [ASCIIZ(asciizdata)|HNUM(hexdata)] SYSTEM The OS2SYS.INI file is to be updated or was the source for the text data file. USER The OS2.INI file is to be updated or was the source for the text data file. filename The path and filename of the .INI file, other than OS2SYS.INI or OS2.INI, to be created or updated or from which the text data file was created. APP Specify the name of the application program that will access the data. KEY Specify the name for the data. The application uses this name to access the data. KEY must be paired with either an ASCIIZ keyword or an HNUM keyword. ASCIIZ Specify the displayable data to be associated with the name in KEY. The data is expected to be in ASCIIZ format (the LINI program appends the necessary zero termination byte to the data as it builds the .INI file). Each character occupies a single byte. HNUM Specify the binary data to be associated with the name in KEY, expressed as an even number of hexadecimal digits. Each pair of digits occupies a single byte. Note: Earlier versions of this statement used the keyword DATA. DATA is equivalent to HNUM and, if encountered, is accepted by the LINI program. DEFINE_PROFILE statements produced by the DINI program now use the keyword HNUM for this data. For example, to associate the data $4Q4DMN to the dataname LOGON_DOMAIN, to associate the binary data 00 to the dataname Bitmap, and the binary data 0100 to the dataname Bitma2, for the application LM_WORKSTATION, use: DEFINE_PROFILE INI_FILE(USER) APP(LM_WORKSTATION) KEY(LOGON_DOMAIN) ASCIIZ($4Q4DMN) KEY(Bitmap) HNUM(00) KEY(Bitma2) HNUM(04) The data is changed if it already exists, and added if it does not already exist. Note that the binary 00 is expressed as 2 hexadecimal digits (also 00) to satisfy the requirement for pairs of hexadecimal digits. To delete any given KEY pair (KEY/ASCIIZ or KEY/HNUM), specify a null data value for the ASCIIZ or HNUM parameter. Example: DEFINE_PROFILE INI_FILE(USER) APP(LM_WORKSTATION) KEY(LOGON_DOMAIN) ASCIIZ() Deleting the last remaining KEY pair in an application deletes the APP keyword and name as well. To delete all the KEY pairs (and thus delete the APP statement), specify a single KEY pair with null values. Either of the examples below will delete all KEY pairs belonging to the application, and will delete the APP statement itself. DEFINE_PROFILE INI_FILE(USER) APP(LM_WORKSTATION) KEY() ASCIIZ() - or - DEFINE_PROFILE INI_FILE(USER) APP(LM_WORKSTATION) KEY() HNUM() ΓòÉΓòÉΓòÉ 15.4.4. DELETE_GROUP ΓòÉΓòÉΓòÉ DELETE_GROUP is used to remove an entire group. This removes all programs from the group and deletes the group definition. Note: The concept of "group" does not apply to the OS/2 2.0 .INI files, unless you migrated from OS/2 1.3 to OS/2 2.0. DELETE_GROUP INI_FILE(SYSTEM|USER|filename) TITLE(groupname) SYSTEM The group to be deleted is in the OS2SYS.INI file. USER The group to be deleted is in the OS2.INI file. filename The path and filename of the .INI file, other than OS2SYS.INI or OS2.INI, that contains the group to be deleted. groupname The name of the group to be deleted. Example: Delete the group REXX from the OS2SYS.INI file. DELETE_GROUP INI_FILE(SYSTEM) TITLE(REXX) Note: A PROTECTED group must be redefined as UNPROTECTED before a program can be deleted from it, and therefore before the group can be deleted. DEFINE_GROUP INI_FILE(SYSTEM) TITLE(REXX) VISIBILITY(VISIBLE+UNPROTECTED) DELETE_GROUP INI_FILE(SYSTEM) TITLE(REXX) ΓòÉΓòÉΓòÉ 15.4.5. DELETE_PROGRAM ΓòÉΓòÉΓòÉ DELETE_PROGRAM is used to remove a program from an OS/2 1.3 Desktop Manager group. DELETE_PROGRAM INI_FILE(SYSTEM|USER|filename) GROUP(groupname) TITLE(progname) SYSTEM The program to be deleted is in the OS2SYS.INI file. USER The program to be deleted is in the OS2.INI file. filename The path and filename of the .INI file, other than OS2SYS.INI or OS2.INI, that contains the program to be deleted. groupname The name of the group that contains the program to be deleted. progname The name of the program to be deleted. Example: Delete the program File Manager from the group Main in the user file TEMP.INI. DELETE_PROGRAM INI_FILE(temp.ini) GROUP(Main) TITLE(File Manager) Note: A PROTECTED group must be redefined as UNPROTECTED before a program can be deleted from it. The group can then be redefined as PROTECTED again. DEFINE_GROUP INI_FILE(temp.ini) GROUP(Main) VISIBILITY(VISIBLE+UNPROTECTED) DELETE_PROGRAM INI_FILE(temp.ini) GROUP(Main) TITLE(File Manager) DEFINE_GROUP INI_FILE(temp.ini) GROUP(Main) VISIBILITY(VISIBLE+PROTECTED) ΓòÉΓòÉΓòÉ 16. Bindery Services ΓòÉΓòÉΓòÉ The NetWare bindery is in a special format that is not viewable with an ordinary text editor. LMU/2 supplies a special utility, LMULOAD.NLM, that enables you to view or update the values of the LMU/2 properties in the bindery. ΓòÉΓòÉΓòÉ 16.1. LMULOAD.NLM ΓòÉΓòÉΓòÉ ΓöÇΓöÇΓöÇ LOAD [volume:path] LMULOAD ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LMULOAD.NLM Command Syntax LMULOAD.NLM displays the current LMU/2 bindery property values and enables you to modify the values. The bindery property values are initialized during customization. The properties are: MANAGING SYSTEM The internetwork address of the OS/2 machine that monitors the heartbeat status of this NetWare Server. DATABASE MACHINE The internetwork address of the OS/2 machine that is the managing system with database, or database machine. This is the station that receives data from the LMU/2 management applications and places the data in the LMU/2 database. The station named must be running the managing system software (LMUSRV), must maintain an LMU/2 database, and can be the same station as MANAGING SYSTEM. FAULT MANAGER The internetwork address of the OS/2 machine to which the LMU/2 management applications in the NetWare Server routes generic alerts for handling. The station named must be running the LMU/2 fault manager software and must have a user-defined table of alerts in the station. PULSE RATE The interval, in minutes, for heartbeat messages from LMUCLI in the NetWare Server to the managing system. A value of 0000 specifies that only the initialization and termination messages are sent. The value is in hexadecimal, four digits. LMU/2 INSTALL DIRECTORY The volume and path of the LMU/2 software in this NetWare Server. LMU/2 DOS DIRECTORY The drive and path of the vital product information file written by the LMU/2 QDOSVPD program for later use by the QUERYVPD.NLM program. LMU/2 MESSAGE LOG The volume, path, and file name of the LMU/2 message log on this NetWare Server. ΓòÉΓòÉΓòÉ 17. Using the LAN Management Utilities/2 Database ΓòÉΓòÉΓòÉ The LAN Management Utilities/2 (LMU/2) database is an IBM OS/2 Database Manager database that is created and maintained by a managing system. It contains tables of configuration data collected by the QUERYVPD and QDOSVPD utilities, and performance data collected by the PERFCAP utility. The database tables and views are described in LAN Management Utilities/2 Database Tables. Continue with the next page in this section. ΓòÉΓòÉΓòÉ 17.1. Creating the Database ΓòÉΓòÉΓòÉ The first time LMUSRV is started in a system (which by definition must be a managing system), it automatically creates the LMU/2 database, using the LMU/2 default database name and location if no parameters are specified. See the description of the LMUSRV command in topic LMUSRV to set the name and location you want for the database. Thereafter, use the LMUSRV command with just the /n option to use the database that was created. Continue with the next page in this section. ΓòÉΓòÉΓòÉ 17.2. Accessing the Database ΓòÉΓòÉΓòÉ You view the data using Structured Query Language (SQL) queries. The SQL that is on your OS/2 system can be invoked in several different ways: You can embed your SQL statements in C programs, COBOL programs, REXX programs, or FORTRAN programs, or use IBM Query Manager (part of IBM OS/2 Database Manager). Sample REXX SQL programs are provided on the LAN Management Utilities/2 diskette. The programs are: LMUCOMPN.CMD LMUDISKU.CMD LMUTABLE.CMD Continue with the next page in this section. ΓòÉΓòÉΓòÉ 17.3. Uploading Data to the Host ΓòÉΓòÉΓòÉ You can use the DBMTODB2 sample program supplied with LAN Management Utilities/2 to extract tables from the LMU/2 database, convert them to host IXF format, and upload them to an MVS host through the OS/2 Communications Manager SEND facility. The workstation that is to perform the uploading must have an OS/2 Communications Manager 3270 emulation session active, and must be logged onto the MVS host system. Once the host DB2 database has been prepared (create storage groups, table space, table definitions, and index for the tables), you can import the uploaded tables into the DB2 database using the Query Management Facility (QMF). The DBMTODB2 utility is a REXX program and is shipped as DBMTODB2.SMP on the LAN Management Utilities/2 diskette. Copy DBMTODB2.SMP to the database machine and rename it to DBMTODB2.CMD. If you use a different database name than "LMU2", or want to use different MVS dataset names than userid.IXF.tablename, use a text editor to modify DBMTODB2.CMD to set the database name and MVS dataset names you want to use. After setting the variables in DBMTODB2.CMD, issue the command DBMTODB2 to upload your database tables to the MVS host. DBMTODB2.CMD calls another utility, IXFUTIL, to perform the actual extraction, conversion, and uploading. The IXFUTIL interface is described in IXFUTIL Utility. Important: Configuration data tables should be created with a logical record length of 4500 bytes, and performance data tables a length of 448 bytes, to avoid segmentation. You may accomplish this by specifying LRECL:4500 or LRECL:448, as appropriate, on the call to IXFUTIL. Continue with the next page in this section. ΓòÉΓòÉΓòÉ 17.3.1. Setting the Database and Dataset Names ΓòÉΓòÉΓòÉ Below is the sample DBMTODB2.CMD file. /*----------------------------------------------------------------------* *-----------------------------------------------------------------------* * DBMtoDB2 Upload the LMU/2 database from DBM to DB/2 for import. * * * * Licensed Materials - Property of IBM * * * * This product contains "Restricted Materials of IBM" * * * * IBM LAN Management Utilities/2 Version 1.00 * * 5799-PLX (C) Copyright IBM Corp. 1991. All rights reserved. * * * * US Government Users Restricted Rights - * * Use, duplication or disclosure restricted by * * GSA ADP Schedule Contract with IBM Corp. * * * * * * ----------------------------------------------------------------------*/ /*----------------------------------------------------------------------* * Sample Rexx procedure to invoke the IXFUTIL Rexx procedure for each * * of the LAN Management Utilities database tables. * * * * Format: * * >>ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ DBMTODB2 ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ * *-----------------------------------------------------------------------*/ Trace o; Parse upper arg arg1 . if (arg1='?' | arg1='H' | arg1='HELP') THEN Do Do i=2 While Left(Sourceline(i),1)<>' ' If i // 20 = 0 Then Do Say 'Press Enter to continue...' Call Linein End Say Sourceline(i) End i Exit End dbname = 'LMU2'; /* default LMU/2 database name */ cfg_tablename.1 = 'ADAPTER'; cfg_dsname.1 = 'IXF.ADAPTER'; cfg_tablename.2 = 'BASE'; cfg_dsname.2 = 'IXF.BASE'; cfg_tablename.3 = 'COMPONENT'; cfg_dsname.3 = 'IXF.COMPONT'; cfg_tablename.4 = 'DISKETTE'; cfg_dsname.4 = 'IXF.DISKETTE'; cfg_tablename.5 = 'DISPLAY'; cfg_dsname.5 = 'IXF.DISPLAY'; cfg_tablename.6 = 'DRIVE'; cfg_dsname.6 = 'IXF.DRIVE'; cfg_tablename.7 = 'FIXED_DISK'; cfg_dsname.7 = 'IXF.FIXEDISK'; cfg_tablename.8 = 'EXPANSION_SLOT'; cfg_dsname.8 = 'IXF.EXPANSON'; cfg_tablename.9 = 'KEYBOARD'; cfg_dsname.9 = 'IXF.KEYBOARD'; cfg_tablename.10 = 'MODEL'; cfg_dsname.10 = 'IXF.MODEL'; cfg_tablename.11 = 'SYSLEVEL'; cfg_dsname.11 = 'IXF.SYSLEVEL'; do i=1 to 11; say 'IXFUTIL Dbname:'dbname' Table:'cfg_tablename.i' Source:OS/2 File:'cfg_dsname.i' Xmit:MVS Quiet' Call IXFUTIL 'Dbname:'dbname' Table:'cfg_tablename.i' Source:OS/2 File:'cfg_dsname.i' Xmit:MVS Quiet' end prf_tablename.1 = 'PROCESS'; prf_dsname.1 = 'IXF.PROCESS'; prf_tablename.2 = 'DISK'; prf_dsname.2 = 'IXF.DISK'; prf_tablename.3 = 'SWAP'; prf_dsname.3 = 'IXF.SWAP'; prf_tablename.4 = 'MEMORY'; prf_dsname.4 = 'IXF.MEMORY'; prf_tablename.5 = 'LOGICAL_DISK'; prf_dsname.5 = 'IXF.LOGICAL'; do i=1 to 5; say 'IXFUTIL Dbname:'dbname' Table:'prf_tablename.i' Source:OS/2 File:'prf_dsname.i' Xmit:MVS Quiet' Call IXFUTIL 'Dbname:'dbname' Table:'prf_tablename.i' Source:OS/2 File:'prf_dsname.i' Xmit:MVS Quiet' end Exit Setting the Database Name To change the DBM database name, look for the line dbname = 'LMU2' and change the "LMU2" to the name of your database. Setting the Dataset Names To change the MVS dataset names that will be used at the host, look for the lines that contain cfg_dsname.n = 'IXF.tablename' and prf_dsname.n = 'IXF.tablename' and change the "IXF.tablename" values to the dataset names that you want to use. Remember that when the tables are uploaded, MVS will append the station userid to the beginning of each dataset name unless you specify otherwise. ΓòÉΓòÉΓòÉ 18. LAN Management Utilities/2 Service Aids ΓòÉΓòÉΓòÉ LAN Management Utilities/2 (LMU/2) provides diagnostics through LAN Management Utilities/2 program messages, some of which are displayed at the station console and some written to a messages log file identified in the LMU.INI file. The location and name of the station's message log file can be customized through the station's LMU control file (keyword MESSAGE_LOG) and the LINI program (see Preparing the Environment). To aid in problem determination, specify a unique log file name and location in each station's LMU.INI file (that is, do not write the messages from multiple stations into a central log file). A log file named LMU.LOG will be created in the root directory of the station's C: drive and used by the LMU/2 programs if: o No log file is specified in the LMU.INI file in the station o LMU/2 programs running in the station cannot access the messages log file specified by the LMU.INI file in the station. If no room remains on the disk, no log file is created, and an error message is presented on the station console. The first level of analysis should be the LMU/2 log file. In the event of any kind of startup or transport problem, a time-stamped message is written to the log file indicating the cause of the problem. If you suspect that the managed systems are receiving the commands, but are not sending the information back to the managing system, check the log in the managed system. If the managed system is not receiving the commands, check the log in the managing system. Some of the messages contain return codes, which are documented in the following manuals: o IBM Operating System/2 LAN Server Version 1.3 Application Programmer's Reference o IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference o IBM Local Area Network Technical Reference. o Novell NetWare OS/2 Developers Kit. o Novell NetWare C interface - DOS. If you do not have these books, contact IBM Software Support or Novell, as appropriate, for help with the meaning of the return codes. ΓòÉΓòÉΓòÉ 19. Using LMU/2 2.0 with Earlier Versions ΓòÉΓòÉΓòÉ Version 1.0 of LMU/2 can coexist with LMU/2 Version 2.0 on the same LAN. With some restrictions, the Version 1.0 and 2.0 LMU/2 systems can communicate with each other. The following tables illustrate the communication capabilities between the different versions of LMU/2 systems. ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Communication Between Managing and Γöé Γöé Managed Systems Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé LMU/2 V1 Γöé LMU/2 V2 Γöé Γöé Γöé Managed Γöé Managed Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé LMU/2 V1 Managing Γöé X Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé LMU/2 V2 Managing Γöé X Γöé X Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Communication Between Administrator Γöé Γöé Workstation and Managed Systems Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé LMU/2 V1 Γöé LMU/2 V2 Γöé Γöé Γöé Managed Γöé Managed Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé LMU/2 V1 Γöé Γöé Γöé Γöé Administrator WS Γöé X Γöé X Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé LMU/2 V2 Γöé X* Γöé X Γöé Γöé Administrator WS Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ * Requires LMU/2 LMUCLIV1.EXE from Version 2 diskette applied to LMU/2 V1 managed systems. ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Communication Between Fault Manager Γöé Γöé and Fault Reporter Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé LMU/2 V1 Γöé LMU/2 V2 Γöé Γöé Γöé Fault Γöé Fault Γöé Γöé Γöé Reporter Γöé Reporter Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé LMU/2 V1 Γöé X Γöé Γöé Γöé Fault Manager Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé LMU/2 V2 Γöé X Γöé X Γöé Γöé Fault Manager Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ 20. Migrating from an Earlier Version of LMU/2 ΓòÉΓòÉΓòÉ If you are migrating from LMU/2 Version 1.0 to LMU/2 Version 2.0, there are some differences you need to be aware of: o LMU/2 database: - The default LMU/2 database names are different. o V1 default database name is LMU o V2 default database name is LMU2 You may need to change the database name in some of your commands. - Some fields in the database have changed. The size and type of some configuration fields have changed, and new fields and tables have been added. If you want to use the data from your existing database, you need to transfer the data to the LMU/2 V2 database. o LMU/2 control file for LMU.INI: New keys have been added to the control file, to support the new LMU/2 applications and functions. You need to add these keys to your existing control file. Existing keys may be modified, and new keys can be added to the end of your control file. The order (sequence) of the keys in the LMU/2 control file is not significant. o Alerts table: - The alerts table has two new fields. You need to run the alert table conversion utility TABCONV.CMD on your existing alerts table. - New parameters have been added for the command string, to pass on the name of the source computer and the SV-Parm text with the alert. o New features: - Supports Novell NetWare workstations running IBM OS/2 or IBM DOS - Enables formatted user data in LMU/2 database, retrievable with SQL queries. To use, create a USERVPD.CFG file and set up some related files. See the sections on the USERVPD.DAT file in this document for details. - Reports user-identified Micro Channel adapters not yet known to the LMU/2 query programs. To use, create ADAPTERS.DEF file. - Monitors critical files in a workstation. To use, create CRITFILES.DEF file. - Monitors critical application programs in a workstation. To use, create APPWATCH table and use the APPWATCH program. ΓòÉΓòÉΓòÉ 20.1. Transferring Data to the New Database ΓòÉΓòÉΓòÉ LMUSRV, when executed with no parameters, will set up the database tables at the first running and thereafter will store received data in that database. As the LMU/2 applications run, data is added to, or replaced in, the LMU/2 database. You can broadcast a QUERYVPD /r command to all OS/2 stations (and run QDOSVPD /r on all DOS stations) to load the database with configuration data for all the workstations. It is not necessary to load the LMU/2 V2 database with data from the LMU/2 V1 database in order for LMU/2 2.0 to operate correctly. Transfer the data to the new database only if you want to. Configuration Data To place configuration data from the LMU/2 V1 database into the LMU/2 V2 database, you need to write a program to do the following: 1. Select all the columns from all the tables (this requires multiple selects) in the V1 database. 2. File the data in a temporary file. 3. Close the V1 database. 4. Open the V2 database. 5. Insert the data from the temporary file into the columns in the tables in the v2 database. Performance Data These tables did not change. To place performance data from the V1 database into the V2 database, you can write a program similar to that described for configuration data, or you can just export the performance data from the V1 database to a file and then import the data from the file to the V2 database. You should do this before you run any PERFCAP /r commands. ΓòÉΓòÉΓòÉ 20.2. Alert Table Conversion ΓòÉΓòÉΓòÉ Two new fields have been added to the user-defined alerts table: Automation Interval Timer and Notification Interval Timer. A conversion utility has been provided to convert your existing alerts table to the new format. To run the utility, enter TABCONV filespec from the command line of an OS/2 workstation, where filespec is the complete drive, path, and filename of the V1 alerts table. You will be prompted for the values to use for the new fields. The utility makes a backup copy of the alerts table (filename.BAK) before reformatting the table. DO NOT RUN THIS UTILITY AGAINST AN ALERT TABLE THAT HAS ALREADY BEEN REFORMATTED. ΓòÉΓòÉΓòÉ 21. LMU/2 Messages ΓòÉΓòÉΓòÉ LMU/2 messages are presented in this appendix in the following order: o Unnumbered messages (messages beginning with words), in alphabetical order o Numbered messages, in alphanumerical order. Each message number consists of 3 letters followed by 4 digits (AUEnnnn, LMUnnnn, and so forth). In addition, the messages are grouped into convenient ranges. Return to the Table of Contents and select the topic whose range includes the message you are looking for. ΓòÉΓòÉΓòÉ 21.1. Unnumbered Messages (A - K) ΓòÉΓòÉΓòÉ ==> Buffer overflow. Line nn is too long. Meaning: Input HNUM() statement (or DATA statement) is too long (8 KB maximum). User Response: Correct the data in the HNUM statement and try again. ==> Corrected NULL directory for program progname in group grpname Meaning: Null directory pointer was encountered in source .INI file. Pointer was corrected in output text file to point to a null string. The original .INI file is not changed. As a result, the .INI file built or updated from the text file will have a different size and contents from the original .INI file. The difference is not an error. User Response: None required. ==> Corrected NULL environment for program progname in group grpname Meaning: Null environment variable pointer was encountered in source .INI file. Pointer was corrected in output text file to point to a null string. The original .INI file is not changed. As a result, the .INI file built or updated from the text file will have a different size and contents from the original .INI file. The difference is not an error. User Response: None required. ==> Corrected NULL icon for program progname in group grpname Meaning: Null icon file pointer was encountered in source .INI file. Pointer was corrected in output text file to point to a null string. The original .INI file is not changed. As a result, the .INI file built or updated from the text file will have a different size and contents from the original .INI file. The difference is not an error. User Response: None required. ==> Corrected NULL parameters for program progname in group grpname Meaning: Null program parameters pointer was encountered in source .INI file. Pointer was corrected in output text file to point to a null string. The original .INI file is not changed. As a result, the .INI file built or updated from the text file will have a different size and contents from the original .INI file. The difference is not an error. User Response: None required. ==> Error in input data. Invalid hexadecimal data: line nn, position cc. Meaning: HNUM() statement (or DATA statement) at line number nn, column cc, contained a character that was not 0-9, A-F. Data in this statement must be an even number of hexadecimal characters. User Response: Correct the statement and try again. ==> Error in input data. Missing hexadecimal digit: line nn. Meaning: HNUM() statement (or DATA statement) at line number nn contained an unpaired hexadecimal character. The statement must contain an even number of hexadecimal characters. User Response: Correct the statement and try again. ==> Error opening input file filename Meaning: Probable cause: resource contention, file locked by another process, file does not exist. User Response: Clear up the contention, or try again later. If this message was produced by the LINI program, correct the datafile name and try again. ==> Error reading datafile Meaning: Probable cause: resource contention, file locked by another process, file does not exist. User Response: Clear up the contention or correct the datafile name, and try again. ==> Error while adding program information for group grpname, program progname Meaning: Probable cause: resource contention. More information may be given if a system message accompanies this error. If the .INI file was being updated, the problem may be a corrupted .INI file. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while creating group grpname Meaning: Probable cause: resource contention. More information may be given if a system message accompanies this error. If the .INI file was being updated, the problem may be a corrupted .INI file. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while deleting group grpname Meaning: Probable cause: resource contention. More information may be given if a system message accompanies this error. If the .INI file was being updated, the problem may be a corrupted .INI file. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while deleting program information for group grpname, program progname Meaning: Probable cause: resource contention. More information may be given if a system message accompanies this error. If the .INI file was being updated, the problem may be a corrupted .INI file. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while opening user profile Meaning: Probable cause: resource contention. More information may be given if a system message accompanies this error. If the .INI file was being updated, the problem may be a corrupted .INI file. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying application appname, key keyname data Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying application appname, key keyname data size Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying application appname key list Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying application appname key list size Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying application list Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying application list size Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying group list Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying group list size Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying program details Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying program details size Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying program list Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while querying program list size Meaning: Probable cause: resource contention or corrupted .INI file. More information may be given if a system message accompanies this error. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while updating group grpname Meaning: Probable cause: resource contention. More information may be given if a system message accompanies this error. If the .INI file was being updated, the problem may be a corrupted .INI file. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Error while updating profile info for application appname, key keyname Meaning: Probable cause: resource contention. More information may be given if a system message accompanies this error. If the .INI file was being updated, the problem may be a corrupted .INI file. User Response: Clear up the contention or try again later. If the file is corrupted (no resource contention but this error still occurs), rebuild or replace the .INI file. ==> Input .INI file filename does not exist. Meaning: Probable cause: wrong file name specified for the input .INI file. User Response: Check the command format, correct the command parameters, and try again. ==> Input .INI file filename is empty or has invalid content. Meaning: Probable cause: wrong file specified as the input .INI file. User Response: Check the command format, correct the command parameters, and try again. ==> Invalid option: opt Meaning: User invoked program with undefined option. No processing occurred. User Response: Check the command format, correct the option, and try again. ΓòÉΓòÉΓòÉ 21.2. Unnumbered Messages (LMUCUST) ΓòÉΓòÉΓòÉ ==> LMUCUST: arg is not a valid parameter. Enter LMUCUST ? for HELP Meaning: An unexpected parameter was given on the command line. User Response: Review the LMUCUST syntax, correct the parameters, and reissue the command. ==> LMUCUST: USERVPD.SMP is on your dirname subdirectory. See the User's Guide for more information concerning modifying USERVPD.SMP to make a USERVPD.DAT file. Meaning: The configuration data programs (QDOSVPD and QUERYVPD) use the USERVPD.DAT file to provide user-supplied data with the configuration data that is sent to the LMU/2 database. The USERVPD.DAT file is optional. User Response: If you want to use a USERVPD.DAT file for this machine, copy or rename the provided sample to USERVPD.DAT and modify it to include the information you want. Note: It is advisable that the first installer modify the shipped sample to create a template that will be meaningful for your installation. This will provide a more consistent method of data gathering as well as more readable, searchable entries in the LAN Management Utilities/2 database. ==> LMUCUST: Cannot update STARTUP.CMD. You must manually add a CALL C:\LMU2\LMUSTART.CMD line to your STARTUP.CMD. Meaning: A backup of your STARTUP.CMD could not be made; therefore, your STARTUP.CMD file was not updated. Probable cause: STARTUP.CMD is locked by another process or does not exist. User Response: Either end the process that has the file locked, or create a STARTUP.CMD that contains the line CALL C:\LMU2\LMUSTART.CMD. ==> LMUCUST: Cannot locate line in STARTUP.CMD that starts the Server/Requester. You must manually add CALL C:\LMU2\LMUSTART.CMD to your STARTUP.CMD. Meaning: LMUCUST attempted to insert the call to LMUSTART.CMD in the STARTUP.CMD file but was unable to do so for one of the following reasons: o The line accessing the remote disk could not be located. o The line starting the server or requester could not be located. User Response: Add the line CALL C:\LMU2\LMUSTART.CMD to your STARTUP.CMD file after the lines that start the server and requester, or after the NET USE command that accesses the disk containing the LMU/2 code. Make sure the server or requester is up and running before you issue the call. If the contents of your STARTUP.CMD file are written in REXX, enclose the call statement in single quotes. ==> LMUCUST: CONFIG.SYS has been saved to C:\LMU2\CONFIG.BAK. Meaning: A backup of CONFIG.SYS was made before CONFIG.SYS was modified. User Response: None. ==> LMUCUST: Customization complete. Restart the computer to activate changes. Meaning: The system has been successfully configured. The system must be restarted for the changes to take effect. User Response: Restart the workstation before using any LMU/2 functions. ==> LMUCUST: Error opening new CONFIG.SYS for output. Meaning: The temporary file used to create the updated CONFIG.SYS could not be opened. Probable cause: No disk space, or too many files in the C:\ directory. User Response: Free some disk space or remove some entries from the C:\ directory. ==> LMUCUST: Error opening old CONFIG.SYS for input. Meaning: The file could not be opened. Probable cause: File locked by another process. User Response: End the process that has the file locked. ==> LMUCUST: Error creating new STARTUP.CMD. Meaning: The temporary file used to create the updated STARTUP.CMD could not be opened. Probable cause: No disk space, or too many files in the C:\ directory. User Response: Free some disk space or remove some entries from the C:\ directory. ==> LMUCUST: Error opening STARTUP.CMD for input. Meaning: The file could not be opened. Probable cause: File locked by another process. User Response: End the process that has the file locked. ==> LMUCUST: File error creating C:\LMU2\LMUSTART.CMD. Meaning: A file error occurred while trying to create the file. Probable cause: Disk full, or the file already exists and either is locked or is read only . User Response: If the disk is full, free some disk space. If the file is locked, end the process that has the file locked. If the file is read only, reset the file attribute. ==> LMUCUST: LMU.INI file created. Meaning: As part of the customization, LINI.EXE was executed using a predefined control file as input. User Response: None. ==> LMUCUST: Modify LMUCTL.SMP in your C:\LMU2 subdirectory and run LINI.EXE with your modified version as input. See the User's Guide for more information. Meaning: A sample control file (LMUCTL.SMP) was copied to the C:\LMU2 directory and should be modified to represent this workstation's control information. Running LINI.EXE with the modified control file as input will produce the required C:\LMU.INI file. User Response: Make a control file for this workstation using the sample provided. Run LINI.EXE with the modified file, to produce the LMU.INI file. Make sure the LMU.INI file is in the C: root directory. ==> LMUCUST: SPATH not specified or SPATH specifies A: drive. Meaning: The user has specified that the LMU files reside on the A: drive or is trying to configure from the A: drive without specifying the LMU file location. User Response: Configure from the disk where the files have been installed or use the SPATH parameter to specify the drive and directory where the LMU/2 software will reside after configuration. ==> LMUCUST: STARTUP.CMD has been saved to C:\LMU2\STARTUP.BAK. Meaning: A backup of your current STARTUP.CMD file was made before the file was modified. User Response: None. ==> LMUCUST: SYSnnnnn error copying file filename. Meaning: An OS/2 system error occurred while trying to copy the file identified in the message. User Response: o Use the OS/2 HELP command for the SYS message number and follow the instructions given. o Record the information in the message and contact IBM Software Support. ==> LMUCUST: SYSnnnnn error copying file file1 to USERVPD.DAT Meaning: An OS/2 system error occurred while trying to copy the file identified in the message. User Response: o Use the OS/2 HELP command for the SYS message number and follow the instructions given. o Record the information in the message and contact IBM Software Support. ==> LMUCUST: SYSnnnnn error copying file file1 to file2. Meaning: An OS/2 system error occurred while trying to copy the file identified in the message. User Response: o Use the OS/2 HELP command for the SYS message number and follow the instructions given. o Record the information in the message and contact IBM Software Support. ==> LMUCUST: SYSnnnnn error creating subdirectory dirname Meaning: An OS/2 system error occurred while trying to create the C:\LMU2 subdirectory. User Response: o Use the OS/2 HELP command for the SYS message number and follow the instructions given. o Record the information in the message and contact IBM Software Support. ==> LMUCUST: Your customized USERVPD.DAT has been copied from pathfile Meaning: A predefined USERVPD.DAT was found and will be used for this workstation. Pathfile is the drive, path, and filename of the file that was the source for USERVPD.DAT. User Response: None. ==> LMUCUST: Your LMU.INI file is being backed up to C:\LMU2\LMU.BAK. Meaning: A backup of your current LMU.INI file was made before the file was modified. User Response: None. ==> LMUCUST: NO_FOLD_GROUP option requires ADMINISTRATOR. Meaning: ADMINISTRATOR must be specified when specifying NO_FOLD_GROUP. User Response: Run LMUCUST with the ADMINISTRATOR option also specified. ==> LMUCUST: Must specify FAULT_MANAGER with NETVIEW, LAN_MANAGER, or NO_FORWARD. Meaning: In order to forward alerts to IBM NetView or LAN Network Manager, or to not forward alerts, the workstation must also be a Fault Manager. In order to be a fault manager the FAULT_MANAGER parameter must be specified. User Response: Run LMUCUST with the FAULT_MANAGER option also specified. ==> LMUCUST: No folder/group will be built when specifying spath. Meaning: The ADMINISTRATOR workstation being customized will not have a folder or group built because the spath parameter was used. Usually, a folder will be built for OS/2 V2.0 workstations and a group will be built for OS/2 V1.3 workstations. LMUGUI.EXE must be installed and its location known before a folder or group will be built. If spath is specified, LMUCUST can not determine if LMUGUI.EXE is installed: a folder or group will not be built. User Response: None ==> LMUCUST: group could not be created. A group will not be built. Meaning:An LMUGROUP.CTL file is generated by LMUCUST in order to create a group on OS/2 1.3 workstations. An error occured when attempting to open this file for output. Some possible causes are: not having write access to the disk where LMUGROUP.CTL is being written, or running out of disk space. o group - LMUGROUP.CTL User Response: Determine why this file could not be opened for output, correct the problem, and try again. ==> LMUCUST: Building of LMU/2 group aborted by OS/2 with rc = os2err . Meaning: An LMUGROUP.CTL file is generated by LMUCUST in order to create a group on OS/2 1.3 workstations. An unexpected termination code was returned from DosExecPgm when attempting to run the LINI program using LMUGROUP.CTL as the input control file. o os2err - the termination code from DosExecPgm User Response: If you have a copy, look up the return code in the IBM OS/2 Programming Reference to determine why LINI terminated abnormally. You may need to restart your system and try again. If the error recurs, record the information in this message and contact IBM Software Support. ==> LMUCUST: Failure while building LMU/2 group; rc from program = lini_rc. Meaning: When executing LINI with a DosExecPgm an error condition was detected by LINI. o program - LINI.EXE o lini_rc - LINI.EXE return code User Response: If you have a copy, look up the return code in the IBM OS/2 Programming Reference to determine why LINI terminated abnormally. You may need to restart your system and try again. If the error recurs, record the information in this message and contact IBM Software Support. ==> LMUCUST: USERVPD.DAT was successfully generated using configfile. Meaning: A prebuilt .CFG file was used to generate this workstation's USERVPD.DAT file. o configfile - name of file used to generate USERVPD.DAT User Response: None ΓòÉΓòÉΓòÉ 21.3. Unnumbered Messages (LMUGETCF) ΓòÉΓòÉΓòÉ ==> LMUGETCF: Unable to access LMU/2 dllname Meaning: LMUGETCF tried to call the named dynamic link library. User Response: Ensure that the directory containing LMU/2 programs is included in LIBPATH in CONFIG.SYS. ==> LMUGETCF: Fatal program error at line line, REXX RC = return code Meaning: A syntax error was encountered in LMUGETCF.CMD. User Response: Contact IBM Software Support. ==> LMUGETCF: OCUNODE RC = return code Meaning: The OCUNODE program returned a non-zero return code. OCUNODE was unable to extract the workstation configuration. User Response: Check the computername.ERR file for details on the failure. ==> LMUGETCF: LMUXFER RC = return code Meaning: The LMUXFER program returned a non-zero return code. LMUXFER was unable to transmit the workstation configuration to the designated Managing System. User Response: Check the LMU.LOG for related communications failure messages. ==> LMUGETCF: parameter is an unrecognized parameter. Meaning: LMUGETCF was started with parameter parameter, which is not a valid parameter; LMUGETCF is terminated. User Response: See the LMUGETCF command description for the command format and valid parameters. ==> LMUGETCF: No Remote Managing System specified Meaning: The /R parameter was not specified, and there is no entry in LMU.INI for Managing System with Database. User Response: Use the /R parameter, or update LMU.INI with Managing System with Database. ΓòÉΓòÉΓòÉ 21.4. Unnumbered Messages (LMUINST) ΓòÉΓòÉΓòÉ ==> LMUINST: THE LMU/2 INSTALLATION IS COMPLETE. Meaning: The installation completed successfully. User Response: Prepare the customization files, then run the customization program (LMUCUST). ==> LMUINST: parameter is an unrecognized parameter. Meaning: The LAN Management Utilities/2 installation program (LMUINST) was started with parameter parameter, which is not a valid parameter; installation is terminated. The parameter may have been mistyped. User Response: See the LMUINST command description for the command format and valid parameters. ==> LMUINST: one or more parameters (ALL IBM NETWARE MANAGING GUI DOC) must be specified. Meaning: The LAN Management Utilities/2 installation program (LMUINST) requires at least one of the listed parameters. Installation is terminated. User Response: See the LMUINST command description for the command format and parameters. ==> LMUINST: Error - Attempting to install from sourcedir to destdir Meaning: The source directory installing from and the destination subdirectory installing to are the same subdirectory. Installation is terminated. User Response: Change the destination drive as specified in the /Tx parameter. /Tx defaults to the boot drive. ==> LMUINST: Error creating subdirectory path; rc = returncode Meaning: The LMU2 subdirectory on the specified target drive could not be created. Installation is terminated. returncode is the return code from the OS/2 MKDIR command. User Response: Specify a valid disk with the /Tx parameter. ==> LMUINST: LMU/2 is now being installed. Meaning: The LMU/2 installation has started. User Response: None. ==> LMUINST: Error copying file file to directory Meaning: An error occurred while trying to copy the file identified in the message. Installation is terminated. User Response: Specify a valid disk with the /Tx parameter. ==> LMUINST: Copying file Meaning: LMUINST is copying the named file to the target disk. The rightmost character in file is the OS/2 wildcard character `?'. This convention allows LMUINST to process both packed and unpacked files. User Response: None. ==> LMUINST: File copy failed; return code = return code Meaning: An error occurred copying the file in the previous message. Installation continues. return code is the return code from the OS/2 UNPACK command. User Response: Ensure that sufficient disk space is available on the target drive. If installing from the LMU/2 installation diskettes and return code is 1, contact IBM Software Support. ==> LMUINST: Files not installed: file1... Meaning: The listed files could not be installed. Either the files listed could not be found on the installation diskettes or source directory, or the target drive ran out of space. User Response: Ensure that sufficient disk space is available on the target drive. Check the LMUINST.LOG in the target directory for more information. ==> LMUINST: Unable to access LMU/2 dllname Meaning: LMUINST tried to call the named dynamic link library. User Response: Ensure that the directory containing LMU/2 programs is included in LIBPATH in CONFIG.SYS. ==> LMUINST: Fatal program error at line line, REXX RC = return code Meaning: A syntax error was encountered in LMUINST.CMD. User Response: Contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.5. Unnumbered Messages (LMUPAGE) ΓòÉΓòÉΓòÉ ==> LMUPAGE: Unable to access LMU/2 dllname Meaning: LMUPAGE tried to call the named dynamic link library. User Response: Ensure that the directory containing LMU/2 programs is included in LIBPATH in CONFIG.SYS. ==> LMUPAGE: Fatal program error at line line, REXX RC = return code Meaning: A syntax error was encountered in LMUPAGE.CMD. User Response: Contact IBM Software Support. ==> LMUPAGE: Message exceeds maximum length Meaning: The combined length of the Pageid and Message exceeded 41 characters. User Response: Shorten the message. ==> LMUPAGE: Page request failed, returned: response Meaning: LMUPAGE could not send the page request through the LMU/2 Fault Managment system. Response is the return string from AUEREXGA. User Response: Ensure that AUEPITCH is executing. Check the LMU.LOG for additional information. ==> LMUPAGE: Page request accepted Meaning: The page request has been accepted by the LMU/2 Fault Management system. User Response: None. ΓòÉΓòÉΓòÉ 21.6. Unnumbered Messages (LMUPAGER) ΓòÉΓòÉΓòÉ ==> LMUPAGER: Cannot open paging system data file file Meaning: PAGESYS.DAT could not be found in the directory containing LMUPAGER.EXE. User Response: Create PAGESYS.DAT in the same directory as LMUPAGER.EXE. ==> LMUPAGER: Cannot open pager user data file file Meaning: PAGEUSR.DAT could not be found in the directory containing LMUPAGER.EXE. User Response: Create PAGEUSR.DAT in the same directory as LMUPAGER.EXE. ==> LMUPAGER: Could not find user Pageid Meaning: Pageid is not defined in PAGEUSR.DAT. User Response: Create an entry for Pageid in PAGEUSR.DAT, or enter an already defined Pageid. ==> LMUPAGER: 'AT' command set modem must be attached and ready Meaning: The modem is not responding. User Response: Ensure that an 'AT' command set modem is attached to the appropriate communications port, as defined in PAGESYS.DAT, and that it is powered on and reset to factory defaults. ==> LMUPAGER: too few parameters Meaning: LMUPAGER requires two parameters, Pageid and Message. User Response: See the LMUPAGER command description for the command format and valid parameters. ==> LMUPAGER: too many parameters Meaning: LMUPAGER requires two parameters, Pageid and Message. If Message contains any special characters, including spaces, it must be enclosed in double quotes ("). User Response: See the LMUPAGER command description for the command format and valid parameters. ==> LMUPAGER: failed, rc = return code: Pageid Message Meaning: The page request could not be sent. Prior messages define the failure. User Response: Check LMU.LOG for related error messages. ==> LMUPAGER: Error opening port Meaning: DOSOPEN failed for the communications port. User Response: Ensure that no other program is using the communications port, and that the appropriate device driver (COM0x.SYS) is installed in CONFIG.SYS. ==> LMUPAGER: Port setup error Meaning: Initialization failed for the communications port. Prior messages define the failure. User Response: Ensure that no other program is using the communications port, that the appropriate device driver (COM0x.SYS) is installed in CONFIG.SYS and that an 'AT' command set modem is attached to the communications port. ==> LMUPAGER: Page request transmitted Meaning: The page request has been successfully transmitted to the paging service. User Response: None. ==> LMUPAGER: IN: received data Meaning: When executed from the command line, LMUPAGER writes a trace of the data transmitted and received. This is useful diagnosing initial setup problems with a paging service. User Response: None. ==> LMUPAGER: OUT: transmitted data Meaning: When executed from the command line, LMUPAGER writes a trace of the data transmitted and received. This is useful diagnosing initial setup problems with a paging service. User Response: None. ==> LMUPAGER: >>> modem status <<< Meaning: The modem has signalled modem status (for example, CONNECT 2400). This is useful diagnosing initial setup problems with a paging service. User Response: None, unless the response differs from what is expected (for example, CONNECT 1200 when 2400 is specified in PAGESYS.DAT). ΓòÉΓòÉΓòÉ 21.7. Unnumbered Messages (M - Z) ΓòÉΓòÉΓòÉ ==> Memory allocation error Meaning: Probable cause: insufficient memory. User Response: Free some memory in the machine and rerun the program. ΓòÉΓòÉΓòÉ 21.8. Numbered Messages (AUE0001 - AUE0020) ΓòÉΓòÉΓòÉ AUE0001E func_id: DosMakeMailslot failed. Rc = returncode. Meaning: The func_id was unable to create a mailslot. The DosMakeMailslot call returned with the return code indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 LAN Server Version 1.3 Application Programmer's Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0002E func_id: DosReadMailslot failed. Rc = returncode. Meaning: The func_id was unable to read the mailslot. The DosReadMailslot call returned with the return code indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 LAN Server Version 1.3 Application Programmer's Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0003E func_id: DosWriteMailslot failed. Rc = returncode. Meaning: The func_id was unable to write to the mailslot. The DosWriteMailslot call returned with the return code indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 LAN Server Version 1.3 Application Programmer's Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0004W func_id: DosGetShrSeg failed, Rc = returncode. Meaning: The func_id was unable to access the shared segement of storage. The DosGetShrSeg call returned with the return code indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 LAN Server Version 1.3 Application Programmer's Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0005E func_id: Adapter number failed to open. Rc = returncode. Meaning: The open call for adapter number failed to open the adapter. The reason for the failure is indicated by returncode. Alerts will not be forwarded. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0006E func_id: Service Access Point failed to open. Rc = returncode. Meaning: The service access point (SAP) failed to open. The reason for the failure is indicated by returncode. Alerts will not be forwarded. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0007E func_id: Frame transmission failed. Rc = returncode. Meaning: The alert data could not be transmitted. The reason for the failure in indicated by the returncode. The alert was not transmitted. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0008E func_id: Reset of adapter number failed; Rc = returncode. Meaning: The reset of the adapter failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0011E func_id: Error allocating shared segment Rc = returncode. Meaning: A segment of shared storage failed to be allocated to func_id. The reason for the failure is indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0014E func_id: LmuSend failed. Rc = returncode. Meaning: The LAN Management Utilities/2 transport failed with the return code indicated. User Response: See the LMU2nnn message that may have accompanied this message, for the meaning of the return code. Take action as indicated in the LMU2nnn message. AUE0015E Error opening filespec Meaning: Could not open the user-written alerts table (identified by filespec) for read operations. User Response: Make sure you have defined an alerts-processing table; make sure the FAULT_TABLE entry in the fault manager LMU.INI file specifies the correct name and location of the table. AUE0016W Table entry recnum greater than 200 bytes. Meaning: The table entry at record number recnum in the user-written alerts table is greater than 200 bytes in length. The entry will be ignored. User Response: Correct the entry and retry the operation. AUE0017W Field 1 of record recnum has an invalid length; length must be 7 alphanumeric characters. Record recnum will be ignored. Meaning: Field 1 of record number recnum in the user-written alerts table must be the Product ID, and must be 7 characters. Either the field is the incorrect length or the record has fields missing (incorrect format). User Response: Correct the entry and retry the operation. AUE0018W Field 2 of record recnum has an invalid length; length must be 2 hexadecimal characters. Record recnum will be ignored. Meaning: Field 2 in record number recnum in the user-written alerts table must be the alert type, and must be 2 characters. Either the field is the incorrect length or the record has fields missing (incorrect format). User Response: Correct the entry and retry the operation. AUE0019W Field 3 of record recnum has an invalid length; length must be 4 hexadecimal characters. Record recnum will be ignored. Meaning: Field 3 of record number recnum in the user-written alerts table must be the alert description, and must be 4 characters. Either the field is the incorrect length or the record has fields missing (incorrect format). User Response: Correct the entry and retry the operation. AUE0020W Field 4 of record recnum has an invalid length; length must be 1 to 8 alphanumeric characters. Record record number will be ignored. Meaning: Field 4 of record number recnum in the user-written alerts table must be the source computer name, and must be 1 to 8 characters. Either the field is the incorrect length or the record has fields missing (incorrect format). User Response: Correct the entry and retry the operation. ΓòÉΓòÉΓòÉ 21.9. Numbered Messages (AUE0021 - AUE0055) ΓòÉΓòÉΓòÉ AUE0021W Field 5 of record recnum has an invalid length; length must be 1 to 8 alphanumeric characters. Record record number will be ignored. Meaning: Field 5 of record number recnum in the user-written alerts table must be the target computer name, and must be 1 - 8 characters. Either the field is the incorrect length, or the record has fields missing (incorrect format). User Response: Correct the entry and retry the operation. AUE0022W Field 6 of record recnum has an invalid length, length must be 5 characters. Record recnum will be ignored. Meaning: Field 6 of record number recnum in the user-written alerts table must be the automation threshold parameters, and must be 5 characters: 4 numeric and 1 alphabetic (for example, 0000Y). The alphabetic character must be Y, y, N, or n. User Response: Correct the entry and retry the operation. AUE0023W Automation reset indicator of record recnum is invalid. Valid values are: y, Y, n, or N. Record recnum automation reset indicator will be set to Y. Meaning: This is the alphabetic character in the 5-character automation threshold parameter of record number recnum in the user-written alerts table. It must be either y, Y, n, or N. User Response: Correct the entry and retry the operation. AUE0024W Field 7 of record recnum has an invalid length, length must be 5 characters. Record recnum will be ignored. Meaning: Field 7 of record number recnum in the user-written alerts table must be the notification threshold parameters, and must be 5 characters: 4 numeric and 1 alphabetic (for example, 0000Y). The alphabetic character must be Y, y, N, or n. User Response: Correct the entry and retry the operation. AUE0025W Notification reset indicator of record recnum is invalid. Valid values are: y, Y, n, or N. Record recnum notification reset indicator will be set to Y. Meaning: This is the alphabetic character in the 5-character notification threshold parameter of record number recnum in the user-written alerts table. It must be either y, Y, n, or N. User Response: Correct the entry and retry the operation. AUE0026W Field 10 of record recnum has an invalid length, length must be 2 hexadecimal characters. Record recnum will be ignored. Meaning: Field 8 of record number recnum in the user-written alerts table must be the alert subvector for which the subfield 82 value is to be retrieved. The field must be 2 numeric characters. User Response: Correct the entry and retry the operation. AUE0027W Subvector value specified in record recnum is invalid. Meaning: Valid values are: 00, 93, 94, 95, or 96. The subvector value will be set to 00 in record number recnum in the user-written alerts table. User Response: Correct the entry and retry the operation. AUE0028E func_id: DosFreeSeg failed, Rc = returncode. Meaning: func_id failed to free storage previously acquired. The reason for the failure is indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0030E func_id: Unable to find FAULT_MANAGER. Meaning: The environment variable FAULT_MANAGER was not found by func_id. User Response: Ensure the environment variable FAULT_MANAGER is set for the machine id which is the fault manager. AUE0032E func_id: Fault Manager variable unavailable in .INI file. Meaning: The function func_id was unable to obtain the value of the FAULT_MANAGER from the LMU.INI file. User Response: Ensure the value is in the LMU.INI file. Also, check the message log for other related LMU error messages. AUE0033E func_id: Fault Table filespec not found in LMU.INI file. Meaning: The function func_id was unable to obtain the value of the FAULT_TABLE from the LMU.INI file. User Response: Ensure the value is in the LMU.INI file. Also, check the message log for other related LMU error messages. AUE0034I func_id: Fault Table filespec is filespec. Meaning: The filespec of the user alert table currently loaded is filespec. User Response: None. AUE0036W func_id: Error code code not supported. Meaning: The function func_id was passed an error code code that is not known to the function. User Response: Record the information in this message and contact IBM Software Support. AUE0037W Field 8 of record recnum has an invalid length, length must be 4 numeric characters. The value will be defaulted to 0000. Meaning: Field 8 of record number recnum in the user-written alerts table is the timer interval for thresholding alert automation. The field must be 2 numeric characters. User Response: None required. AUE0038W Field 9 of record recnum has an invalid length, length must be 4 numeric characters. The value will be defaulted to 0000. Meaning: Field 8 of record number recnum in the user-written alerts table is the timer interval for thresholding alert notification. The field must be 2 numeric characters. User Response: None required. AUE0040E func_id: Application Id length error. Length is length. Meaning: The Application Name passed was greater than 8 characters. User Response: Correct the Application Name and try again; if the problem persists, contact IBM Software Support. AUE0041E func_id: Message length error. Length is length. Meaning: The Message text passed to func_id was greater than 44 characters. User Response: Correct the message text and try again; if the problem persists, contact IBM Software Support. AUE0042E func_id: Name length error. Length is length. Meaning: The Computer ID passed to func_id was greater than 21 characters. User Response: Correct the computer name or NetWare name and try again; if the problem persists, contact IBM Software Support. AUE0050E func_id: Data transfer failed. Rc = returncode. Meaning: The transfer of the alert data to the Communication Manager failed. The reason is indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Extended Edition Version 1.3 APPC Programming Reference for the meaning of the return code and take action as appropriate. AUE0051E Invalid characters in Error_Number parm. Meaning: The REXX program invoking the AUEREXGA external function specified invalid numeric characters in the Error_Code parameter string. User Response: Correct the parameter and retry the operation. AUE0052E Invalid APPL_ID length = nn. Meaning: The REXX program invoking the AUEREXGA external function specified an application name longer than 8 characters in the second parameter string. User Response: Correct the parameter and retry the operation. AUE0053E Message parameter too long. Length = length. Meaning: The REXX program invoking the AUEREXGA external function specified an alert message text longer than 44 characters in the third parameter string. User Response: Correct the parameter and retry the operation. AUE0054E Wrong Number of Strings = string count. Meaning: The REXX program invoking the AUEREXGA external function specified an invalid number of parameter strings. There are two valid formats for the external function. The first has three parameters and the second has four. User Response: See Alert Generation and Routing to determine the proper format for the AUEREXGA function call. Correct the call and retry the operation. AUE0055E Invalid Event_CPU length = nn. Meaning: The REXX program invoking the AUEREXGA external function specified an Event_CPU parameter longer than 8 characters in the fourth parameter string. User Response: Correct the parameter and retry the operation. ΓòÉΓòÉΓòÉ 21.10. Numbered Messages (AUE0056 - AUE0099) ΓòÉΓòÉΓòÉ AUE0056E Return Code from AUEUSRGA = returncode. Meaning: The REXX program invoked the AUEREXGA external function, which received a non-zero return code from AUEUSRGA; the alert was not sent to the fault manager. User Response: Review the LMU/2 message log for an explanation of the error encountered by AUEUSRGA and take the corrective action indicated by the message. AUE0057I func_id: Is currently running on this machine. Meaning: The function func_id is already initialized and running on this machine. User Response: To terminate the function use LMUQUERY /T func_id. Otherwise, let it run. AUE0058E func_id: DosCreateSem failed, Rc = returncode. Meaning: The system semaphore used to control func_id failed. The reason for the failure is indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0070W Potential Virus Detected. Meaning: This message is part of a generic alert sent to IBM NetView or to IBM LAN Network Manager. A virus checker detected the presence of a potential virus in a workstation and, as a result, the VIRALERT or DOSVIRGA command was executed at the workstation to request the creation of a generic alert. User Response: Follow the actions described in the Recommended Action portion of the alert. ΓòÉΓòÉΓòÉ 21.11. Numbered Messages (AUE0100 - AUE0199) ΓòÉΓòÉΓòÉ AUE0100E func_id: DosCreateQueue failed, Rc = returncode. Meaning: The queue needed by function func_id was not created for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0101W func_id: proc_id processor did not load. Meaning: The function func_id did not load the process proc_id. This is simply an informational warning. User Response: Check the message log if you feel the proc_id should have been loaded for additional messages relating to the load failure. AUE0103E func_id: DosReadQueue failed, Rc = returncode. Meaning: A read of the queue by function func_id failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0104E func_id: DosWriteQueue failed. Rc = returncode. Meaning: A write to the queue by function func_id failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0105W func_id: DosLoadModule failed, Rc = returncode. Meaning: The DosLoadModule call failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0106E func_id: DosGetProcAddr failed, Rc = returncode. Meaning: The DosGetProcAddr call failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0107E func_id: DosAllocSeg failed, Rc = returncode. Meaning: The DosAllocSeg call failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0108E func_id: DosCreateThread failed, Rc = returncode. Meaning: The DosCreateThread call failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0110E func_id: SpxECBErrorCheck failed. Rc = returncode. Meaning: The SpxECBErrorCheck failed for the reason indicated by returncode. User Response: If you have a copy, refer to the API Developer's Guide for NetWare Requester for OS/2 for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0111E func_id: SpxOpenSocket failed. Rc = returncode. Meaning: The SpxOpenSocket failed for the reason indicated by returncode. User Response: If you have a copy, refer to the API Developer's Guide for NetWare Requester for OS/2 for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0112E func_id: SpxListenForConnection failed. Rc = returncode. Meaning: The SpxListenForConnection failed for the reason indicated by returncode. User Response: If you have a copy, refer to the API Developer's Guide for NetWare Requester for OS/2 for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0113E func_id: DosSemSet failed. Rc = returncode. Meaning: The DosSemSet failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0114E func_id: SpxListenForConection API failed. Rc = returncode. Meaning: The SpxListenForConection API failed for the reason indicated by returncode. User Response: If you have a copy, refer to the API Developer's Guide for NetWare Requester for OS/2 for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0115E func_id: DosSemWait failed. Rc = returncode. Meaning: The DosSemWait call failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0118E func_id: CatchQue failed. Rc = returncode. Meaning: The call to CatchQue failed to complete queue initialization. User Response: Check the message log for additional messages relating to the failure. AUE0120E func_id: SpxListenForConnectionPacket failed. Rc = returncode. Meaning: The SpxListenForConnectionPacket call failed for the reason indicated by returncode. User Response: If you have a copy, refer to the API Developer's Guide for NetWare Requester for OS/2 for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0121E func_id: SpxListenForConnectionPacket API failed. Rc = returncode. Meaning: The SpxListenForConnectionPacket API failed for the reason indicated by returncode. User Response: If you have a copy, refer to the API Developer's Guide for NetWare Requester for OS/2 for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0122E func_id: DosGetInfoSeg failed. Rc = returncode. Meaning: The function func_id failed to establish addressability to an item on the functions queue. The reason for the failure is indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0123E func_id: DosOpenQueue failed. Rc = returncode. Meaning: The work queue for function func_id could not be opened. The reason is indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0124E func_id: DosGiveSeg failed. Rc = returncode. Meaning: The function func_id failed to transfer an item of work. The reason for the failure is indicated by returncode. User Response: If you have a copy, refer to the IBM Operating System/2 Programming Tools and Information Version 1.3 Control Program Programming Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0125E func_id: Invalid data received. Meaning: Data received by func_id is invalid. User Response: This is quite likely an internal programming error. Contact IBM Software Support. AUE0126E func_id: NCB.RESET failed, Rc = returncode. Meaning: The Netbios NCB.RESET used to initialize the resources failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0127E func_id: NCB.ADD.NAME failed, Rc = returncode. Meaning: The Netbios NCB.ADD.NAME failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0128E func_id: NCB.LISTEN failed, Rc = returncode. Meaning: The Netbios NCB.LISTEN failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0129E func_id: NCB.RECEIVE failed, Rc = returncode. Meaning: The Netbios NCB.RECEIVE failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0130E func_id: NCB.HANG.UP failed, Rc = returncode. Meaning: The Netbios NCB.HANG.UP failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. AUE0131W func_id: NCB.RESET failed, Rc = returncode. Meaning: The Netbios NCB.RESET used to exit and terminate failed for the reason indicated by returncode. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.12. Numbered Messages (EXQnnnn) ΓòÉΓòÉΓòÉ For any messages beginning with EXQ, contact IBM Support (1-800-237-5511) with the following information: Product: LMU/2 Graphical User Interface (GUI) The message number The task you were attempting to accomplish The active window or panel ΓòÉΓòÉΓòÉ 21.13. Numbered Messages (LMULOG1 - LMULOG7) ΓòÉΓòÉΓòÉ LMULOG1 Unable to obtain the name of LMU/2 log file, rc = returncode Meaning: An attempt to log an LMU/2 message has failed. The name of the log file cannot be located. The original error message follows this message. User Response: Run LMULOAD to determine if the LMU/2 message log key value has been specified. If not, add it and continue processing. If this does not resolve the problem, record the contents of this messsage and contact IBM Software Support. LMULOG2 Error opening LMU/2 log file filename errornumber Meaning: An attempt to open the LMU/2 log file filename failed. The original error message follows this message. User Response: If errornumber is 1 the path of the log file is incorrect. Ensure that the volume and directory specified are correct and exist. If this does not resolve the problem, record the contents of this messsage and contact IBM Software Support. LMULOG3 Error closing LMU/2 log file filename errornumber Meaning: An attempt to close the LMU/2 log file filename failed. The original error message follows this message. User Response: Record the contents of this messsage and contact IBM Software Support. LMULOG4 Error seeking LMU/2 log file filename errornumber Meaning: An error occured while processing the LMU/2 log file filename. The original error message follows this message. User Response: Record the contents of this messsage and contact IBM Software Support. LMULOG5 Error positioning LMU/2 log file filename errornumber Meaning: An error occured while processing the LMU/2 log file filename. The original error message follows this message. User Response: Record the contents of this messsage and contact IBM Software Support. LMULOG6 Error reading LMU/2 log file filename errornumber Meaning: An error occured while reading the LMU/2 log file filename. The original error message follows this message. User Response: Record the contents of this messsage and contact IBM Software Support. LMULOG7 Error writing LMU/2 log file filename errornumber Meaning: An error occured while writing to the LMU/2 log file filename. The original error message follows this message. User Response: Record the contents of this messsage and contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.14. Numbered Messages (LMU0001 - LMU0080) ΓòÉΓòÉΓòÉ LMU0001I LMUSRV initialization complete[; using database dbname] Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has successfully completed initialization. Dbname, if present, indicates the OS/2 Database Manager LMU/2 database in which vital product data and performance data will be recorded. If server alerts are enabled in LMUSRV, LMUSRV sends a generic alert (message LMU0900I) to the fault manager to report this condition. User Response: None. LMU0002I LMUSRV termination complete; reason code = reasoncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has successfully completed termination with reason code reasoncode. If server alerts are enabled in LMUSRV, LMUSRV sends a generic alert (message LMU0901I) to the fault manager to report this condition. User Response: If LMUSRV was not terminated as a result of operator action, examine preceding messages in the message log for the cause of termination. LMU0003E Invalid option opt Meaning: The LAN Management Utilities/2 Server software (LMUSRV) was invoked with option opt, which is not a valid option; processing is terminated. User Response: See the command format in topic LMUSRV, correct the command, and reissue LMUSRV. LMU0004E Invalid value specified for opt option Meaning: The LAN Management Utilities/2 Server software (LMUSRV) was invoked with an invalid value specified for option opt; processing is terminated. User Response: See the command format in topic LMUSRV, correct the command, and reissue LMUSRV. LMU0005E LMUSRV is already executing Meaning: The LAN Management Utilities/2 Server software (LMUSRV) is already executing on this workstation; processing is terminated. User Response: None LMU0006E {DosGetInfoSeg | DosGetEnv | DosSizeSeg} failed processing {system variables | environment} segment; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosGetInfoSeg, DosGetEnv, or DosSizeSeg; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0007E Insufficient storage to allocate stack for tname thread Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected error while attempting to allocate a stack for the thread named tname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU001cE func_id DOS must be present in order to customize the server. Meaning: The DOSPresent call indicated DOS had been removed from the server. User Response: Reboot the system and do not remove DOS. LMU0010W DosWriteMailslot failed sending command to computername; mailslot not defined Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an error from DosWriteMailSlot while attempting to send a command to computer computername; mailslot not defined at computername; processing continues. The probable cause is that LAN Management Utilities/2 Client software (LMUCLI) is not executing in computername; processing continues. User Response: Start LMUCLI in computername. If the problem recurs, record the information in this message and contact IBM Software Support. LMU0011W DosWriteMailslot failed sending command to computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosWriteMailslot while attempting to send a command to computer computername; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0012W Invalid target (targetname) specified by computername; command discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) could not forward the command sent by computername to targetname because the required requester is not available on targetname. Process continues but the command is discarded. User Response: Record the information in this message and contact IBM Software Support. LMU002cE func_id Unable to create AUTOEXEC.BAT file on the DOS partition. Meaning: The autoexec.bat file could not be created on the DOS partition. User Response: Check the message log for additional error messages, correct any errors found. Otherwise, contact IBM Software Support. LMU0020E {DosLoadModule | DosGetProcAddr} failed for {module | function} name; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosLoadModule or DosGetProcAddr for name while sending output to computer computer; processing is terminated. Possible causes for DosLoadModule include the following: o OS/2 Database Manager is not installed o OS/2 LAN Requester or NetWare Requester for OS/2 is not installed o Missing LIBPATH specification in CONFIG.SYS. User Response: For DosLoadModule, install the required software and/or update LIBPATH statement in CONFIG.SYS; reboot, then reissue LMUCMD. Otherwise, record the information in this message and contact IBM Software Support. LMU003cE Memory allocation for filename failed. Meaning: The memory needed to read filename into storage was not available. User Response: Ensure the file size is reasonable, and that there is enough free memory on the machine to alllocate. LMU0030E DosMakeMailslot failed for mailslot mname; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) ncountered an unexpected return code returncode from DosMakeMailslot for mailslot mname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0031W {DosReadMailslot | DosDeleteMailslot} failed for mailslot mname; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) ncountered an unexpected return code returncode from DosReadMailslot or DosDeleteMailslot for mailslot mname; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU004cE func_id Unable to put dos drive in the bindery. Meaning: The bindery add routine failed to add the value for LMU_DOS_DIR property. User Response: Check the message log for additional error messages and correct any errors found. Otherwise, contact IBM Software Support. LMU0040W Invalid data received; data discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has received invalid data. The data is discarded; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0041W Database request received from computername; database request discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has received a database request from computer computername, but LMUSRV was started with the remote database (/r) option, indicating that LMUSRV is not to maintain a database. The database request is discarded; processing continues. User Response: If the database is located on another workstation, then do the following: 1. In LMU.CTL on computername, correct the MANAGING_SYSTEM_WITH_DATABASE key to identify the workstation that maintains the database. 2. Update the LMU.INI file on computername by executing LINI.EXE. If LMUSRV is to maintain an LMU/2 database, terminate LMUSRV and restart it without the remote database (/r) option. LMU0042I Termination request received from computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has received an LMUQUERY request from computername to terminate. User Response: None LMU0043W Invalid request (type xxxx) received from computername; request discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has received a type xxxx request, which is invalid, from computer computername. The request is discarded; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0044W Insufficient storage to convert migration request from computername; migration request discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected error while allocating storage to convert the migration request from computername to a Version 2.x request. Processing continues but the migration request from computername is discared. User Response: Record the information in this message and contact IBM Software Support. LMU005cE func_id Open error errorcode on file filename. Meaning: The file filename failed to open. The reason is indicated by the errorcode. User Response: If you have a copy, refer to the Network C for NLMs Software Developer's Kit for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU0050E {DosCreateThread | DosSetPrty |DosExitList} failed for tname thread; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosCreateThread, DosSetPrty, or DosExitList for thread tname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0051E {DosCreateQueue | DosOpenQueue | DosWriteQueue | DosReadQueue | DosCloseQueue} failed for queue qname; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosCreateQueue, DosOpenQueue, DosWriteQueue, DosReadQueue, or DosCloseQueue for queue qname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0052E Insufficient storage to allocate work area for tname thread Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected error while allocating a work area for thread tname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0053W Insufficient storage to process data from tname thread; data discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected error while allocating a buffer for data received by thread tname; Processing continues but the data is discarded. User Response: Record the information in this message and contact IBM Software Support. LMU0054E Profile error getting value for required key keyname; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for the key identified by keyname in the LMU.INI file; processing is terminated. There may be a problem in the LMU.INI file. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. If values were missing, correct the LMU/2 control file. 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU0055W Profile error getting value for key keyname; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for the key identified by keyname in the LMU.INI file; processing continues. There may be a problem in the LMU.INI file. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. If values were missing, correct the LMU/2 control file. 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU0056W DosFreeSeg failed for selector sel; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosFreeSeg for selector sel; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0057E {DosCreateSem | DosCloseSem} failed for system semaphore semaphore; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosCreateSem or DosCloseSem for system semaphore semaphore; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0058E NetServerGetInfo failed; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from NetServerGetInfo; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU006cE func_id Read error errorcode on file filename. Meaning: The read operation on filename failed. The reason is indicated by the errorcode. User Response: If you have a copy, refer to the API Developer's Guide for NetWare Requester for OS/2 for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU0061E {SpxOpenSocket | SpxCloseSocket} failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from the indicated SPX function; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0062W DosSemWait for {SpxListenForConnection | SpxListenForConnectionPacket | SpxTerminateConnection} failed; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosSemWait for the indicated SPX function; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0063W {SpxECBErrorCheck | SpxListenForConnection | SpxGetConnectionStatus | SpxListenForConnectionPacket | SpxTerminateConnection} failed; {rc | status}%2 = X'code' Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code or status code from the indicated SPX function; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0064W IpxGetLocalTarget failed for internetwork address internetaddr; rc = X'returncode' Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from IpxGetLocalTarget while attempting to find a route to internetwork address internetaddr; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0065W Invalid SPX packet received from computername; data discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has received an invalid SPX packet from computername; processing continues but the data is discarded. User Response: Record the information in this message and contact IBM Software Support. LMU0066W SPX packet sequence number error detected on connection with computername; data discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has detected a pakcet sequence error on connection with computername; processing continues but the data is discarded. User Response: Record the information in this message and contact IBM Software Support. LMU0067W Insufficient space to receive SPX packet from computername; data discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has received an SPX packet that would make the current data request too large; processing continues but the data is discarded. User Response: Record the information in this message and contact IBM Software Support. LMU0068W IpxSend failed sending command to computername; rc = X'returncode' Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from IpxGetLocalTarget while attempting to find a route to internetwork address internetaddr; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU007cE func_id Unable to get LMU/2 directory from the bindery. Meaning: The function func_id failed to obtain the value of the property LMU_HOME_DIR. User Response: Check the message log for additional error messages and correct any errors found. Otherwise, contact IBM Software Support. LMU0070E Routine failed for database dbname; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from OS/2 Database Manager routine routine for database dbname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0071E Create failed for database dbname {table | view} name; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode creating table or view name for database dbname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0072E SQL COMMIT failed for database dbname creation; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from SQL COMMIT while creating database dbname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0073W SQL statement failed for database dbname table tname processing data from computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from SQL statement statement for database dbname table tname while processing data from computer computername; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0074W SQL {COMMIT | ROLLBACK} failed for database dbname processing configuration data from computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from SQL COMMIT or ROLLBACK for database dbname while processing configuration data from computer computername; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0075E SQLGBIND failed binding filename to database dbname; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode binding file filename to the OS/2 Database Manager database identified by dbname; processing is terminated. Possible causes include the following: o Incorrect path was specified for the BIND key in LMU.INI. o One or more bind files (filename) are missing or invalid. Note: LMUSRVDB.BND contains a list of bind file names - one of these files may be the problem. User Response: Ensure that the path specified for the BIND key in LMU.INI is correct and that all bind files exist in that directory. LMU0076W SQL COMMIT failed for database dbname processing change log for computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from SQL COMMIT while processing the change log for computer computername (database is dbname); processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0077W Invalid database data (type xxxx) received from computername; database data discarded Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has received type xxxx database data, which is invalid, from computer computername. The database data is discarded; processing continues. User Response: Record the information in this message and contact IBM Software Support. * LMU008cE func_id Unable to get dos drive from the bindery. Meaning: The function func_id failed to obtain the value of the property LMU_DOS_DIR User Response: Check the message log for additional error messages and correct any errors found. Otherwise, contact IBM Software Support. LMU0080W {DosChgFilePtr | DosClose | DosOpen | DosWrite} failed for file filename processing change log for computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosChgPtr, DosClose, DosOpen, or DosWrite for change log filename; processing continues but change log entry for computer computername is not processed. User Response: Record the information in this message and contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.15. Numbered Messages (LMU0081 - LMU0999) ΓòÉΓòÉΓòÉ LMU0081W Profile error getting value for key keyname processing change log for computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for key keyname in the LMU.INI file; processing continues, but the change log entry for computer computername is not processed. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. Correct the LMU/2 control file if necessary 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU0082W Maximum data rows exceeded reading database dbname table tname for computername; maximum = mnum Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered excessive data rows reading database dbname table tname for computer computername. The maximum number of data rows allowable is mnum. Processing continues but additional data rows are ignored. User Response: Record the information in this message and contact IBM Software Support. LMU0083W Invalid slot number (snum) encountered reading database dbname table tname for computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an invalid slot number (snum) while reading database dbname table tname for computer computername; processing continues but invalid data rows are ignored. User Response: Record the information in this message and contact IBM Software Support. LMU0084W Insufficient storage to read additional data rows from database dbname table tname for computername; data rows read = rows Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected error allocating storage to read more than rows data rows from database dbname table tname for computername; processing continues but additional data rows are ignored. User Response: Record the information in this message and contact IBM Software Support. LMU0085I Configuration change detected for computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) in the managing system with database detected a configuration change for computer computername. The managing system with database will record the change in the change log. If change log alerts are enabled in LMUSRV, the managing system with database sends a generic alert (message LMU0905I) to the fault manager to report this condition. User Response: Examine the change log and, if necessary, correct the configuration at computername. LMU0086W Error invoking change log filter program LMUSRVFL.CMD for computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode calling the change log filter program LMUSRVFL.CMD for computername; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0090W Invalid heartbeat request (type xxxx) received from computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has received an invalid heartbeat notification (type xxxx) from computer computername. The heartbeat notification is discarded; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0091W Insufficient storage to register computername with thread tname Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an error allocating storage to register computer computername with thread tname; processing continues but service for computername may be incomplete. User Response: Record the information in this message and contact IBM Software Support. LMU0092I {Initial | Terminating} heartbeat received from computername Meaning: The LAN Management Utilities/2 server software (LMUSRV) has received an initial or terminal heartbeat notification from computer computername; processing continues. If heartbeat alerts are enabled in LMUSRV, LMUSRV sends a generic alert (message LMU0902I for initial or message LMU0903I for terminating) to the fault manager to report this condition. User Response: None. LMU0093W Insufficient storage to process update for computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected error allocating storage to update the LAN Management Utilities/2 Graphical User Interface software (LMUGUI) about the managed system computername. Processing continues but the information presented by LMUGUI will be incomplete. User Response: Record the information in this message and contact IBM Software Support. LMU0100E DosSleep failed; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosSleep; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU0101W Heartbeat overdue from computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has not received a heartbeat notification from computer computername within the allowable time interval; processing continues. If heartbeat alerts are enabled in LMUSRV, LMUSRV sends a generic alert (message LMU0904W) to the fault manager to report this condition. User Response: If computer computername is a critical resource, then perform problem determination and restart the LAN Management Utilities/2 Client software (LMUCLI) on computername. LMU0110W Insufficient storage to invoke user exit Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected error allocating storage to invoke the user exit; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0111W DosStartSession failed processing user exit; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosStartSession; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0120W OS/2 LAN Server not started; migration support disabled Meaning: The LAN Management Utilities/2 Server software (LMUSRV) detected that the OS/2 LAN Server program is not executing on the workstation; processing continues but down-level managed system will not be able to communication with LMUSRV. User Response: If down-level managed systems are present, terminate LMUSRV, start the OS/2 LAN Server and then restart LMUSRV. LMU0130E {NCB.RESET | NCB.ADD.NAME} for adapter adpnum failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from the indicated NETBIOS function using adapter adpnum; processing is terminated. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the NETBIOS return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU0131W {NCB.LISTEN | NCB.RECEIVE | NCB.HANG.UP} for adapter adpnum failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from the indicated NETBIOS function using adapter adpnum; processing continues. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the NETBIOS return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU0140W DosAllocSeg failed for nbytes bytes; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosAllocSeg attempting to allocate nbytes; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0150W {DosWriteQueue | DosReadQueue} failed for queue qname; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosWriteQueue or DosReadQueue for queue qname; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0160W Invalid inquiry request (type xxxx) received from computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) has received type xxxx inquiry request, which is invalid, from computer computername. The inquiry request is discarded; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0161W Insufficient storage to register computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an error allocating storage to register the LAN Management Utilities/2 Graphical User Interface software (LMUGUI) executing on computer computername; processing continues but service for computername may be incomplete. User Response: Record the information in this message and contact IBM Software Support. LMU0162W Insufficient storage to process inquiry from computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an error allocating storage to build a reply for an inquiry request from computername; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0170W {DosOpen | DosWrite | DosClose} failed for file fname from computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosOpen, DosWrite, or DosClose processing file fname from computername; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU0171W cbytes of ebytes bytes written to file fname from computername Meaning: The LAN Management Utilities/2 Server software (LMUSRV) detected a byte mismatch after transfering file fname from computername. The size of fname was ebytes but cbytes were written; processing continues but the contents of fname may be incorrect. User Response: Record the information in this message and contact IBM Software Support. LMU0180I Error sending update for client to computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from the LAN Management Utilities/2 Send software (LMUSEND) while attempting to send an update for client to the LAN Management Utilities/2 Graphical User Interface software (LMUGUI) on computername; processing continues. User Response: Verify that the LAN Management Utilities/2 Graphical User Interface software (LMUGUI) is executing on computer computername. LMU0190W Error sending reply to computername; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from the LAN Management Utilities/2 Send software (LMUSEND) while attempting to send a reply to an inquiry from computername; processing continues. User Response: Verify that the LAN Management Utilities/2 Graphical User Interface software (LMUGUI) is executing on computer computername. LMU0900I Initialization complete Meaning: If server alerts are enabled in LMUSRV, LMUSRV sends this message in a generic alert to the fault manager to report that LMUSRV completed initialization with no errors. User Response: None. LMU0901I Termination complete Meaning: If server alerts are enabled in LMUSRV, LMUSRV sends this message in a generic alert to the fault manager to report that LMUSRV completed termination. User Response: None. LMU0902I Initial heartbeat received Meaning: If heartbeat alerts are enabled in LMUSRV, LMUSRV sends this message in a generic alert to the fault manager whenever an initial heartbeat notification is received from the LAN Management Utilities/2 client software (LMUCLI). User Response: None LMU0903I Terminating heartbeat received Meaning: If heartbeat alerts are enabled in LMUSRV, LMUSRV sends this message in a generic alert to the fault manager whenever a terminating heartbeat notification is received from the LAN Management Utilities/2 client software (LMUCLI). User Response: None. LMU0904W Heartbeat overdue Meaning: If heartbeat alerts are enabled in LMUSRV, LMUSRV sends this message in a generic alert to the fault manager whenever a heartbeat notification is not received from the LAN Management Utilities/2 client software (LMUCLI) within the allowable time interval specified in LMU.INI. User Response: If this alert is received for a critical resource, then perform problem determination and restart LAN Management Utilities/2 Client software (LMUCLI) on indicated computer. LMU0905I Configuration changed Meaning: If change log alerts are enabled in LMUSRV in a managing system with database, LMUSRV sends this message in a generic alert to the fault manager whenever a configuration change is detected for a managed system. User Response: Examine the change log on the managing system with database and, if necessary, correct the configuration at the computer identified in the generic alert. LMU0999W DosGetMessage failed for message msgnum in file msgfile; rc = returncode Meaning: The LAN Management Utilities/2 Server software (LMUSRV) encountered an unexpected return code returncode from DosGetMessage for message number msgnum; processing continues. User Response: When returncode is 2, verify that the message file msgfile is in the current directory or accessable via DPATH. Otherwise, record the information in this message and contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.16. Numbered Messages (LMU1000 - LMU1499) ΓòÉΓòÉΓòÉ LMU1000I LMUCLI initialization complete Meaning: The LAN Management Utilities/2 client software (LMUCLI) has successfully started. User Response: None LMU1001E DosExitList setup failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to add an exit list routine. LMUCLI is terminated. User Response: Record the return code and contact IBM Software Support. LMU1002E Unable to set screen autodestruction mode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to cause its NLM screen to automatically close. User Response: Record the message information and contact IBM Software Support. LMU1004E DosAllocSeg for heartbeat thread stack segment in computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error allocating storage; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1005E DosCreateThread for heartbeat manager thread in computername failed; rc = returncode. Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error creating a system thread; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1007E DosAllocSeg for communication thread stack segment in computername failed; rc = returncode. Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error allocating storage; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1008E DosCreateThread for mailbox manager thread in computername failed; rc = returncode. Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error creating a system thread; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1009E Unrecognized LMUCLI start option opt. Meaning: An attempt was made to start the LAN Management Utilities/2 client software (LMUCLI) with start parameters. User Response: LMUCLI has no start parameters; restart the program with no options. LMU1015I LMUCLI termination complete Meaning: The LAN Management Utilities/2 client software (LMUCLI) has successfully shut down as a result of a SHUTDOWN request. The request was entered at the command line or received from an administrator workstation. User Response: None. LMU1031E DosMakeMailSlot in computername failed; rc = returncode. Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error while creating a communications mailslot; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1032E DosReadMailSlot in computername failed; rc = returncode. Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error while reading from a communications mailslot; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1033E DosStartSession for pname in computername failed; rc = returncode. Meaning: The LAN Management Utilities/2 client software (LMUCLI) has received a request to run program pname, but return code returncode was received when trying to execute this program. User Response: Determine if pname and all included DLL routines are within the PATH and DPATH environment strings of computername. If the error is not in the environment string, record the information in this message and contact IBM Software Support. LMU1034I LMUCLI shutdown requested from computer computername Meaning: The LAN Management Utilities/2 client software (LMUCLI) has received an LMUQUERY request from computername to shut down. User Response: If this shutdown request is unexpected, contact your system administrator with the shutdown information. LMU1035I DosGetEnv in computername failed; rc = returncode. Meaning: LMUCLI has received an error trying to modify the environment string of a session it is about to start in response to an LMUCMD command. The information normally added to the environment is the COMPUTERNAME from the IBMLAN.INI file in the administrator workstation that issued the LMUCMD command. The environment string actually passed to the program that is to be started will be the environment of LMUCLI. If the program to be started is SHUTDOWN, the bypass pop-up will not be displayed and shutdown will continue. If the program to be started was initiated by the LMUCMD command, output will not be relayed back to the administrator workstation. User Response: Record the information in this message and contact IBM Software Support. LMU1036I DosSizeSeg in computername failed; rc = returncode. Meaning: LMUCLI has received an error trying to modify the environment string of a session it is about to start in response to an LMUCMD command. The information normally added to the environment is the COMPUTERNAME from the IBMLAN.INI file in the administrator workstation that issued the LMUCMD command. The environment string actually passed to the program that is to be started will be the environment of LMUCLI. If the program to be started is SHUTDOWN, the bypass pop-up will not be displayed and shutdown will continue. If the program to be started was initiated by the LMUCMD command, output will not be relayed back to the administrator workstation. User Response: Record the information in this message and contact IBM Software Support. LMU1037I DosAllocSeg in computername failed; rc = returncode. Meaning: LMUCLI has received an error trying to modify the environment string of a session it is about to start in response to an LMUCMD command. The information normally added to the environment is the COMPUTERNAME from the IBMLAN.INI file in the administrator workstation that issued the LMUCMD command. The environment string actually passed to the program that is to be started will be the environment of LMUCLI. If the program to be started is SHUTDOWN, the bypass pop-up will not be displayed and shutdown will continue. If the program to be started was initiated by the LMUCMD command, output will not be relayed back to the administrator workstation. User Response: Record the information in this message and contact IBM Software Support. LMU1038I DosFreeSeg in computername failed; rc = returncode. Meaning: The LAN Management Utilities/2 client software (LMUCLI) has received an error trying to free storage after modifying the environment string of a session it has started. Processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU1075I LMUCLI process has terminated. Reason code is termcode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has terminated. User Response: If LMUCLI is not terminating as a result of operator action, the message prior to this in the LMU/2 message log indicates the source of the error. Follow the action required for the earlier message. LMU1076E Error obtaining computer name Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error obtaining this workstation's computer name. The name may be missing in the IBMLAN.INI file. Processing is terminated. User Response: The message prior to this in the LMU/2 message log indicates the cause of the failure. Follow the action required for the earlier message. Make sure that the computer name is in the IBMLAN.INI file, and that the workstation is logged on to the domain. LMU1077W Unknown command "xxxxx" received from computer computername Meaning: The LAN Management Utilities/2 client software (LMUCLI) has received a request to run command xxxxx, but the command is unknown; processing continues. User Response: Determine if the command requested is valid and is contained within the PATH and DPATH environment search orders. If not, record the command name and contact your system administrator. LMU1079W Failure to obtain client pulse rate; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error obtaining the heartbeat pulse rate from the LMU/2 profile services; processing continues, using the default pulse rate of zero. LMUCLI will report only its start and termination until the problem has been corrected. User Response: Examine the messages prior to this one in the LMU/2 message log to determine if the LMU.INI file has been corrupted. If so, rebuild the LMU.INI file by running the LINI.EXE program and specifying the LMU/2 control file as input. If the LMU.INI file has not been corrupted, see the LMU3nnn messages earlier in the LMU/2 message log to determine the cause of the problem. LMU1080I Heartbeat pulse failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error sending the heartbeat pulse to the managing system; processing continues. User Response: If returncode is 4, the managing system software (LMUSRV) is not running; have your system administrator start this software in the managing system to enable the heartbeat function. If the heartbeat function is not desired, modify your LMU/2 control file in the LMUCLI station to remove the PULSE_RATE variable, run the LINI.EXE program using this modified LMU/2 control file as input, and restart LMUCLI. LMUCLI will then report only its start and termination to the managing system. LMU1081E Heartbeat DosSleep failed for computername; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during processing of the heartbeat function; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1082E DosSemSet for heartbeat semaphore in computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1083E DosSemWait for heartbeat semaphore in computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1084E DosSemSet for communication manager semaphore in computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1085E DosSemWait for communication manager semaphore in computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1086E LMUCLI window initialization error Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1087E WinCreateMsgQueue in LMUCLI failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1088E WinRegisterClass in LMUCLI failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1089E WinCreateStdWindow in LMUCLI failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1090E LMUCLI already running; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has already been started in this workstation. User Response: None. LMU1091E LMUCLI initialization error; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1092W Terminating heartbeat failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error sending the terminating heartbeat pulse to the managing system; LMUCLI termination continues. User Response: If returncode is 4, the managing system software (LMUSRV) is not running; have your system administrator start LMUSRV in the managing system. If returncode is not 4, record the information in this message and contact IBM Software Support. LMU1094E IpxOpenSocket in computer computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error opening an SPX socket to be used for communication. LMUCLI is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1095E IpxReceive in computer computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error receiving data from the network. LMUCLI is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1096E DosExitList setup for computer computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to add an exit list routine. LMUCLI is terminated. User Response: Record the return code and contact IBM Software Support. LMU1097E Local semaphore in computer computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to add a local semaphore. LMUCLI is terminated. User Response: Record the return code and contact IBM Software Support. LMU1098E IpxReceive in computer computername failed; ecb.status = statuscode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error receiving data from the network. LMUCLI is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1100W IpxCloseSocket in computer computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error closing its IPX socket during LMUCLI termination. Termination continues. User Response: Record the information in this message and contact IBM Software Support. LMU1102E DosOpenSem for communication manager semaphore failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1103E DosExitList setup failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to add an exit list routine. LMUCLI is terminated. User Response: Record the return code and contact IBM Software Support. LMU1104E DosOpenSem failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1105E Error obtaining computer name Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error obtaining this workstation's computer name. The name may be missing in the IBMLAN.INI file. Processing is terminated. User Response: The message prior to this in the LMU/2 message log indicates the cause of the failure. Follow the action required for the earlier message. Make sure that the computer name is in the IBMLAN.INI file, and that the workstation is logged on to the domain. LMU1106E DosCreateSem failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1107E DosCreateQueue failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1108E DosSemSet for command manager semaphore failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1110E SpxOpenSocket in computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1111E SpxListenForConnection in computername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to set up a connection with an administrator workstation. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1112E DosSemSet for command failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1113E DosSemWait for command failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1114E SpxListenForConnection failed; ecb status = statuscode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to read data on a connection from an administrator workstation. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1115E SpxListenForConnectionPacket failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to set up a connection with an administrator workstation. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1116E SpxListenForConnectionPacket failed; ecb status = statuscode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to set up a connection with an administrator workstation. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1119E SpxListenForSequencedPacket in servername failed; rc = returncode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to receive data on a connection with an administrator workstation. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1120E SpxListenForSequencedPacket in servername failed; ecb status = statuscode Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error attempting to receive data on a connection with an administrator workstation. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU1121E Unable to install console handler Meaning: The LAN Management Utilities/2 client software (LMUCLI) has encountered an error during initialization. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.17. Numbered Messages (LMU1500 - LMU1999) ΓòÉΓòÉΓòÉ LMU1500E LMUSTEP is already running in another session. Meaning: The LMU/2 Scheduler (LMUSTEP.EXE) is already running and can not be started again. User Response: No action is required. LMU1501W LMUSTEP schedule file read interval not set in LMU.INI, using default = 60. Meaning: The LMU/2 Schedule file is checked every 60 minutes for change and will be read if there is a change. User Response: The schedule read interval can be set in the LMU.INI file from (1 - n) minutes, if the default of 60 minutes is not desireable. LMU1502W LMUSTEP schedule file path and file name not set in LMU.INI, using default = \LMU2\SCHEDULE.TIM Meaning: The LMU/2 Schedule file is the input file that is used by the LMU/2 Scheduler for the execution schedule. User Response: The schedule file path and file name can be set in the LMU.INI file. LMU1503W LMUSTEP group file path and file name not set in LMU.INI, using default = \LMU2\SCHEDULE.GRP Meaning: The LMU/2 Schedule group is the input file that is used by the LMU/2 Scheduler for the machines and groups. User Response: The schedule group path and file name can be set in the LMU.INI file. LMU1504E Could not allocate shared memory, rc: nnnn Meaning: A error occurred trying to allocate memory. User Response: Free up memory and retry. LMU1505E Could not prepare shared memory for sub-allocation, rc: nnnn Meaning: A error occurred trying to allocate memory. User Response: Free up memory and retry. LMU1506E Could not allocate stack for command thread, rc: nnnn Meaning: A error occurred trying to allocate memory. User Response: Free up memory and retry. LMU1507I Resolved: (FILE NAME) Meaning: The LMU/s schedule file was tested for a change since the last time that it was read. User Response: No action is required. LMU1508E Can not open (FILE NAME). Please create the file or set the variable in LMU.INI with the correct path and file name. Meaning: The LMU/s schedule file was not found in the path and file name specified. User Response: Create the schedule file or change the path and file name in the LMU.INI file to point to the schedule file. LMU1509I Reading Schedule File: (FILE NAME) Meaning: The LMU/s schedule file has been changed and the new data is being read. User Response: No action is required. LMU1510E Could not sub-allocate shared memory. The QUEUE is full and the following command will be lost: Meaning: The data area for the scheduler is full and will not accept any more commands. 64K bytes of data is the maximum that can be waiting for execution at any time. User Response: Schedule less commands for execution at a specific time. LMU1511E Could not add command to QUEUE. The following command will be lost: Meaning: The data area for the scheduler is full and will not accept any more commands. 64K bytes of data is the maximum that can be waiting for execution at any time. User Response: Schedule less commands for execution at a specific time. LMU1512E Can not open (FILE NAME). Please create the file or set the variable in LMU.INI with the correct path and file name. Meaning: The LMU/s group file was not found in the path and file name specified. User Response: Create the schedule file or change the path and file name in the LMU.INI file to point to the group file. LMU1513E invalid option Meaning: The LMU/2 scheduler detected an invalid destination type for the command scheduled for execution. User Response: Use the lmu/2 schedule editor (LMUSCHED.EXE) to correct the syntax of the command. LMU1514W LMUSTEP log file path and file name not set in LMU.INI, using default = \LMU2\SCHEDULE.LOG Meaning: The LMU/2 Schedule log file is the file that is used to save the results of the commands that are executed by the LMU scheduler. User Response: The scheduler log path and file name can be set in the LMU.INI file. LMU1515E Could not create command QUEUE, rc: nnnn Meaning: An internal QUEUE used by the LMU/2 scheduler could not be created. The return code was from the API call DosCreateQueue. User Response: Try running the application when more QUEUE resources are available LMU1516E Error reading from command QUEUE, rc: nnnn, Command execute thread will be terminated. Meaning: An internal QUEUE used by the LMU/2 scheduler could not be read. The return code was from the API call DosReadQueue. User Response: Try running the application when more QUEUE resources are available. LMU1517E RETURN.DTA File not found. Meaning: An internal file (RETURN.DAT) used by the LMU/2 scheduler could not be found. User Response: Restart the LMU/2 Scheduler. LMU1518E Can not open FILE Meaning: The file name supplied for saving the results of the command executed by the LMU/2 scheduler could not be opened. The path and file name may be invalid or the file may be read only or locked. User Response: Insure that the path and file name are valid and that the file is not read only or locked. LMU1550W LMUSTEP group file path and file name not set in LMU.INI, using default = \LMU2\SCHEDULE.GRP Meaning: The LMU/2 Schedule group is the input file that is used by the LMU/2 Scheduler for the machines and groups. User Response: The schedule group path and file name can be set in the LMU.INI file. LMU1551E Error opening Group file (FILE NAME) for writing. Data will not be saved. Meaning: The group file name could not be opened. The path and file name may be invalid or the file may be read only or locked. User Response: Insure that the path and file name are valid and that the file is not read only or locked. LMU1552E Group file has been modified, Select OK to discard changes. Meaning: The file that was being edited has changed and the QUIT option has been selected. if OK is selected the changes will be lost. User Response: Select OK to discard changes and QUIT or CANCEL to return. LMU1553W Group data length greater then 256 bytes. All groups have been reset. Meaning: The total length of the MACHINE name and all of the assigned groups must not exceed 256 bytes. If this occurs, all groups that were selected will be reset. User Response: Select groups again and insure that the total length in bytes is less then 256. This can be done with shorter machine or group names or fewer groups. LMU1554E Invalid or duplicate machine name entered. Machine can not be added. Meaning: The machine name that was entered already exists and can not be added again. User Response: Enter a name that does not already exist. LMU1554E Invalid or duplicate machine name entered. Machine can not be added. Meaning: The machine name that was entered already exists and can not be added again. User Response: Enter a name that does not already exist. LMU1554E Machine name invalid or not found. Machine can not be deleted. Meaning: The machine name that was entered was not found in the machine list. User Response: Enter a name that exists and retry. LMU1556E Invalid or duplicate group name entered. Group can not be added. Meaning: The group name that was entered already exists and can not be added again. User Response: Enter a name that does not already exist. LMU1556E Group name invalid or not found. Group can not be deleted. Meaning: The machine name that was entered was not found in the machine list. User Response: Enter a name that exists and retry. LMU1600E Error opening Schedule file (FILE NAME) for writing. Data will not be saved. Meaning: The schedule file could not be opened. The path and file name may be invalid or the file may be read only or locked. User Response: Insure that the path and file name are valid and that the file is not read only or locked. LMU1601E All fields not entered. Entry can not be added or modified. Meaning: Data was not entered for all Time and Date fields that require data. User Response: Insure that all Date and Time fields contain valid data. LMU1602E No destination entered. Entry can not be added or modified. Meaning: There was no destination for the Command selected. User Response: Select a destination for the command. LMU1603E No Machine selected. Entry can not be added or modified. Meaning: There was no machine selected with Destination of Machine selected. User Response: Select a machine and continue. LMU1604E No Wait selection made. Entry can not be added or modified. Meaning: Either (Wait) of (No wait) must be selected. User Response: Select (Wait) of (No wait) and continue. LMU1605E No Save file type selected. Entry can not be added or modified. Meaning: Either (Log) of (File) must be selected. User Response: Select (Log) of (File) and continue. LMU1606W Schedule file has been modified, Select OK to discard changes. Meaning: The file that was being edited has changed and the QUIT option has been selected. If OK is selected the changes will be lost. User Response: Select OK to discard changes and QUIT or CANCEL to return. LMU1607W LMUSTEP schedule file path and file name not set in LMU.INI, using default = \LMU2\SCHEDULE.TIM Meaning: The LMU/2 Schedule file is the input file that is used by the LMU/2 Scheduler for the execution schedule. User Response: The schedule file path and file name can be set in the LMU.INI file. LMU1608W LMUSTEP group file path and file name not set in LMU.INI, using default = \LMU2\SCHEDULE.GRP Meaning: The LMU/2 Schedule group is the input file that is used by the LMU/2 Scheduler for the machines and groups. User Response: The schedule group path and file name can be set in the LMU.INI file. LMU1609E No Command was entered. Entry can not be added or modified. Meaning: The Command field must contain valid data. User Response: Enter a Command and continue. LMU1610E The YEAR that was selected is already past. Entry can not be added or modified. Meaning: A command with this Date and Time will never execute. User Response: Enter a Command with the Date and Time in the future. LMU1611E The MONTH that was selected is already past. Entry can not be added or modified. Meaning: A command with this Date and Time will never execute. User Response: Enter a Command with the Date and Time in the future. LMU1612E The DAY that was selected is already past. Entry can not be added or modified. Meaning: A command with this Date and Time will never execute. User Response: Enter a Command with the Date and Time in the future. LMU1613E The DAY that was selected is already past. Entry can not be added or modified. Meaning: A command with this Date and Time will never execute. User Response: Enter a Command with the Date and Time in the future. LMU1614E The MINUTE that was selected is already past. Entry can not be added or modified. Meaning: A command with this Date and Time will never execute. User Response: Enter a Command with the Date and Time in the future. LMU1615E Wait time is missing or invalid. The valid wait times are 0 - 120 seconds. Entry can not be added or modified. Meaning: The Wait time for command execution is missing or invalid. 0 = wait forever, or wait (1 - 120) seconds are the only valid times. User Response: Select or Enter a valid wait time. LMU1616E File name is missing or invalid. Entry can not be added or modified. Meaning: The file name given for the (Log) or (File) type file is missing or invalid. User Response: Enter a valid file name. LMU1617E The MONTH that was entered is invalid. The valid months are jan - dec, or 1 - 12, or * for all valid months. Entry can not be added or modified. Meaning: The MONTH field contains invalid data. User Response: Enter valid data for MONTH. LMU1618E The DAY that was entered is invalid. The valid days are 1 - 31, or * for all valid days. Entry can not be added or modified. Meaning: The DAY field contains invalid data. User Response: Enter valid data for DAY. LMU1619E The HOUR that was entered is invalid. The valid hours are 0 - 23, or * for all valid hours. Entry can not be added or modified. Meaning: The HOUR field contains invalid data. User Response: Enter valid data for HOUR. LMU1620E The MINUTE that was entered is invalid. The valid minutes are 0 - 59, or * for all valid minutes. Entry can not be added or modified. Meaning: The MINUTE field contains invalid data. User Response: Enter valid data for MINUTE. LMU1621E Entry exceeds the limit of 256 bytes. The length must be reduced. Entry can not be added or modified. Meaning: The total length of the command including all fields must not exceed 256 bytes. User Response: Reduce the length of the overall command. LMU1622E No entry is selected to modify. Meaning: An entry in the command list box at the top of the GUI must be selected before it can be modified. User Response: Select an entry, make the desired changes, then press the modify button. LMU1623E No entry is selected to delete. Meaning: An entry in the command list box at the top of the GUI must be selected before it can be deleted. User Response: Select an entry, then press the delete button. LMU1650W LMUSTEP schedule file path and file name not set in LMU.INI, using default = \LMU2\SCHEDULE.TIM Meaning: The LMU/2 Schedule file is the input file that is used by the LMU/2 Scheduler for the execution schedule. User Response: The schedule file path and file name can be set in the LMU.INI file. LMU1651E PRUNETIM error, unable to copying the schedule file: (FILE NAME) Meaning: Schedule file may be missing or the name may be invalid or the file may be locked. User Response: Correct the file name and run again. LMU1652E PRUNETIM error, unable to replace the schedule file: (FILE NAME) Meaning: Schedule file may be locked or read only. User Response: Correct the file attribute and run again. LMU1700W LMU log file path and file name not set in LMU.INI, using default = \LMU.LOG Meaning: The default name is being used for the LMU log file. User Response: The LMU log file path and file name can be set in the LMU.INI file. LMU1701E PRUNELMU error, unable to copying the LMU LOG file: (FILE NAME) Meaning: LMU log file may be missing or the name may be invalid or the file may be locked. User Response: Correct the file name and run again. LMU1702E PRUNELMU error, unable to erase the LMU LOG file. Meaning: LMU log file may be locked or read only. User Response: Correct the file attribute and run again. LMU1703E PRUNELMU error, unable to replace the LMU LOG file: %s The original file was saved in PRUNELMU.DAT and the pruned file is PRUNELMU.NEW Meaning: LMU log file could not be replaced after the pruning operation was completed. User Response: The file can be manually replaced with either the original or the pruned file name that was supplied with the error message. LMU1750W LMUSTEP log file path and file name not set in LMU.INI, using default = \LMU2\SCHEDULE.LOG Meaning: The LMU/2 Schedule log file is the file that is used to save the results of the commands that are executed by the LMU scheduler. User Response: The scheduler log path and file name can be set in the LMU.INI file. LMU1751E PRUNESTP error, unable to copying the Schedule log file: (FILE NAME) Meaning: Scheduler log file may be missing or the name may be invalid or the file may be locked. User Response: Correct the file name and run again. LMU1752E PRUNESTP error, unable to erase the Schedule log file: (FILE NAME) Meaning: Scheduler log file may be locked or read only. User Response: Correct the file attribute and run again. LMU1753E PRUNESTP error, unable to replace the Schedule log file: %s The original file was saved in PRUNESTP.DAT and the pruned file is PRUNESTP.NEW Meaning: Scheduler log file could not be replaced after the pruning operation was completed. User Response: The file can be manually replaced with either the original or the pruned file name that was supplied with the error message. LMU1800W LMU change log file path and file name not set in LMU.INI, using default = \LMUCHG.LOG Meaning: The default name is being used for the LMU change log file. User Response: The LMU Change log path and file name can be set in the LMU.INI file. LMU1801E PRUNECHG error, unable to copying the LMU change log file: (FILE NAME) Meaning: LMU Change log file may be missing or the name may be invalid or the file may be locked. User Response: Correct the file name and run again. LMU1802E PRUNECHG error, unable to erase the LMU change log file: (FILE NAME) Meaning: LMU Change log file may be locked or read only. User Response: Correct the file attribute and run again. LMU1803E PRUNECHG error, unable to replace the LMU change log file: %s The original file was saved in PRUNECHG.DAT and the pruned file is PRUNECHG.NEW Meaning: LMU Change log file could not be replaced after the pruning operation was completed. User Response: The file can be manually replaced with either the original or the pruned file name that was supplied with the error message. LMU1850W LMUSTEP schedule file path and file name not set in LMU.INI, using default = \LMU2\SCHEDULE.TIM Meaning: The LMU/2 Schedule file is the input file that is used by the LMU/2 Scheduler for the execution schedule. User Response: The schedule file path and file name can be set in the LMU.INI file. LMU1851E LMUSTEPU error, Too Few parameters to add an entry to the schedule. The format is: (LMUSTEPU hour minute nth_week week_day month month_day year command) Meaning: A minimun of 8 fields are required to add a command to the schedule. Seven for date and Time and 1 for the command. User Response: Retry with the correct number of parameters. LMU1852E LMUSTEPU error, unable to open the schedule file: (FILE NAME) Meaning: The schedule file could not be opened. The path and file name may be invalid or the file may be read only or locked. User Response: Insure that the path and file name are valid and that the file is not read only or locked. LMU1853E LMUSTEPU error, unable to write to the schedule file: (FILE NAME). bytes written = nnnn Meaning: An error occurred trying to write an entry to the schedule file. User Response: Retry at a later time. LMU1900E Invalid data format, Unexpected '[' found in data Meaning: A data field must be closed with a ']' before another field can be opened with a '['. User Response: Correct the syntax error and retry. LMU1901E Invalid data format, Unexpected ']' found in data Meaning: A data field must be opened with a '[' before it can be closed with a ']'. User Response: Correct the syntax error and retry. LMU1902E Invalid data format, Unexpected '{' found in data Meaning: A data field must be closed with a '}' before another field can be opened with a '{'. User Response: Correct the syntax error and retry. LMU1903E Invalid data format, Unexpected '}' found in data Meaning: A data field must be opened with a '{' before it can be closed with a '}'. User Response: Correct the syntax error and retry. LMU1904E Invalid data format, Unmatched brackets ([]) or ({}) braces found in data, or data greater then 3500 bytes. Meaning: Brackets and braces must be in pairs in input file. Braces outside of brackets will be concidered to be comments. User Response: Correct the syntax error and retry. LMU1905E No data in input file. Meaning: There was no data to convert. The output file will not be created. User Response: Create a file that contains valid user data. LMU1906E User data length exceeds maximum of 3500 bytes. Meaning: The maximum user data that can be saved is 3500 bytes. The output file will not be created. User Response: Reduce the length of the user data to a maximum of 3500 bytes. LMU1907E User data source file (.CFG) name was not entered. Meaning: No source file was entered. User Response: Enter a Source and Target file and retry. LMU1908E User data target file (.DAT) name was not entered. Meaning: No target file was entered. User Response: Enter a Source and Target file and retry. LMU1909E Error opening source data file: (FILE NAME) Meaning: The file name that was supplied could not be opened. User Response: Insure that the path and file name is valid. LMU1910E Error opening target data file: (FILE NAME) Meaning: The file name that was supplied could not be opened. The file name may be invalid, read only, or locked. User Response: Insure that the path and file name is valid and the file is not read only or locked. ΓòÉΓòÉΓòÉ 21.18. Numbered Messages (LMU2000 - LMU2999) ΓòÉΓòÉΓòÉ LMU2011E DosAllocSeg failed; rc = returncode. Meaning: The allocation of memory for the transfer of information between computers failed for reason returncode. User Response: If returncode is 8, the environment is memory constrained; free some memory. If returncode is other than 8, contact IBM Software Support. LMU2013E DosFreeSeg failed; rc = returncode. Meaning: The freeing of memory following the transfer of information between computers failed for reason returncode. User Response: Record the information in this message and contact IBM Software Support. LMU2015E NetWkaStaGetInfo failed; rc = returncode. Meaning: The request to gather LAN Requester characteristics failed for reason returncode. User Response: Ensure that LAN Requester is installed correctly and started. LMU2017E Unable to obtain data value for key key;rc = returncode Meaning: The request to obtain the data value for key Key failed. User Response: Ensure that the LMU.INI file is on the root directory of the boot drive. Run the LINI program to dump the contents of the LMU.INI file and verify that the keys and their values are correct. LMU2018E SpxOpenSocket failed; rc = returncode Meaning: The request to open a SPX socket for machine to machine communication failed. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU2019E OpenLocalSemaphore failed Meaning: An LMU/2 internal error has occured. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU2020E SpxEstablishConnection to internetwork address failed; rc = returncode Meaning: An attempt to establish a connection to internetwork address has failed, processing is terminated. User Response: Ensure that the machine for internetwork address is running. If the target machine is the Managing system, ensure that LMUSRV is running. If the target machine is the Fault Manager, ensure that AUECATCH is running. LMU2021E WaitOnLocalSemaphore failed; rc = returncode Meaning: An internal error has occured, processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU2022E Connection setup to internetwork address failed; ecb status = statuscode Meaning: An attempt to establish a connection to internetwork address has failed, processing is terminated. User Response: Ensure that the machine for internetwork address is running. If the target machine is the Managing system, ensure that LMUSRV is running. If the target machine is the Fault Manager, ensure that AUECATCH is running. LMU2023E SpxSendSequencedPacket to internetwork address failed; rc = returncode Meaning: An attempt to send data to internetwork address has ended abnormally, processing is terminated. User Response: Ensure that the machine for internetwork address is running. If the target machine is the Managing system, ensure that LMUSRV is running. If the target machine is the Fault Manager, ensure that AUECATCH is running. If the machine setup is correct, record the information in this message and contact IBM Software Support. LMU2024E WaitOnLocalSemaphore failed; rc = returncode Meaning: An internal error has occured, processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU2025E SpxSendSequencedPacket to internetwork address failed; ecb status = statuscode Meaning: An attempt to send data to internetwork address has ended abnormally, processing is terminated. User Response: Ensure that the machine for internetwork address is running. If the target machine is the Managing system, ensure that LMUSRV is running. If the target machine is the Fault Manager, ensure that AUECATCH is running. If the machine setup is correct, record the information in this message and contact IBM Software Support. LMU2026E IpxGetInternetworkAddress failed; rc = returncode Meaning: An attempt to determine the local internetwork address has failed. Processing is terminated. User Response: Ensure that the NetWare requester has been installed properly and the the requester is running. If the machine setup is correct, record the information in this message and contact IBM Software Support. LMU2029E SpxCloseSocket failed; rc = returncode Meaning: The request to close a SPX socket being used for machine to machine communication failed. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU2030E DosSemSet for commmunication macro name failed; rc = returncode Meaning: An internal error has occured, processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU2031E DosSemWait for commmunication macro name failed; rc = returncode Meaning: An internal error has occured, processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU2033E DosLoadModule for load module name failed; rc = returncode Meaning: An error occured trying to load load module name processing is terminated. User Response: Ensure that the directory that contains the LMU/2 system modules is in the libpath of your machine. If the machine libpath appears correct, record the information in this message and contact IBM Software Support. LMU2034E DosGetProcAddr for module name failed; rc = returncode Meaning: An internal error has occured, processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU2035E NWGetDefaultConnectionID failed; rc = returncode Meaning: An attempt to determine the local machine connection information has failed. Processing is terminated. User Response: Ensure that the NetWare requester has been installed properly and the the requester is running. If the machine setup is correct, record the information in this message and contact IBM Software Support. LMU2036E NWGetConnectionStatus failed; rc = returncode Meaning: An attempt to determine the local machine connection information has failed. Processing is terminated. User Response: Ensure that the NetWare requester has been installed properly and the the requester is running. If the machine setup is correct, record the information in this message and contact IBM Software Support. LMU2037E NETBIOS macro name in computername failed; rc = returncode Meaning: An attempt to issue macro name has failed. Processing is terminated. User Response: If the macro is RESET with return code 38, increase the number of NETBIOS commands, sessions and names according to the values explained in the NETBIOS section of this book. For other errors, examine the IBM Token Ring technical reference to determine the meaning of the return code, record the information in this message and contact IBM Software Support. LMU2038E NETBIOS macro name in sourcecomputername to targetcomputername failed; rc = returncode Meaning: An attempt to issue macro name to targetcomputername has failed. Processing is terminated. User Response: If the macro is CALL and the return code is 14, ensure that the name of the target machine is correct. If the target machine is the managing system, ensure LMUSRV is running in this machine. If the target machine is the Fault Manager, ensure that AUECATCH is running in this machine. For other errors, examine the IBM Token Ring technical reference to determine the meaning of the return code, record the information in this message and contact IBM Software Support. LMU2039E Connection setup to internetwork address failed; ecb status = statuscode Meaning: An attempt to establish a connection to internetwork address has failed, processing is terminated. User Response: Ensure that the machine for internetwork address is running. If the target machine is the Managing system, ensure that LMUSRV is running. If the target machine is the Fault Manager, ensure that AUECATCH is running. LMU2040E IpxOpenSocket failed; rc = returncode Meaning: The request to open a IPX socket for machine to machine communication failed. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU2041E GetConnectionInformation failed; rc = returncode Meaning: An attempt to determine the local machine connection information has failed. Processing is terminated. User Response: Ensure that the NetWare requester has been installed properly and the the requester is running. If the machine setup is correct, record the information in this message and contact IBM Software Support. LMU2042E SpxSendSequencedPacket to internetwork address failed; ecb status = statuscode Meaning: An attempt to send data to internetwork address has ended abnormally, processing is terminated. User Response: Ensure that the machine for internetwork address is running. If the target machine is the Managing system, ensure that LMUSRV is running. If the target machine is the Fault Manager, ensure that AUECATCH is running. If the machine setup is correct, record the information in this message and contact IBM Software Support. LMU2043E IPXInitialize failed; rc = returncode Meaning: An attempt to initialize IPX communication has failed. Processing is terminated. User Response: Ensure that the NetWare requester has been installed properly and the the requester is running. If the machine setup is correct, record the information in this message and contact IBM Software Support. LMU2044E SPX not installed Meaning: An attempt to initialize SPX communication has failed. Processing is terminated. User Response: Ensure that the NetWare requester has been installed properly and the the requester is running. If the machine setup is correct, record the information in this message and contact IBM Software Support. LMU2045E Unable to allocate Listen ECBs Meaning: The allocation of memory for the transfer of information between computers has failed. User Response: The environment is memory constrained; free some memory. ΓòÉΓòÉΓòÉ 21.19. Numbered Messages (LMU3000 - LMU3999) ΓòÉΓòÉΓòÉ LMU3500W LMU/2 log error occurred during access control Meaning: The LAN Management Utilities/2 log processor has encountered an error trying to obtain access privilege for the LAN Management Utilities/2 log file. The error message log is in an unpredictable state. Processing continues. User Response: Record the error message and contact IBM Software Support. LMU3501W LMU/2 log error occurred, default log C:\LMU.LOG being used Meaning: The LMU/2 log processor has encountered an error trying to obtain the name of the LMU/2 log file from LMU/2 profile services. The default log is now being used. Processing continues. User Response: Examine the messages prior to this one in the LMU/2 message log to determine if the LMU.INI file has been corrupted. If so, rebuild the LMU.INI file by running the LINI.EXE program and specifying the LMU/2 control file as input. If the LMU.INI file has not been corrupted, or if rebuilding the file does not correct the problem, record the error message and contact IBM Software Support. LMU3502W LMU/2 log error occurred trying to open log file filename Meaning: The LAN Management Utilities/2 log processor has encountered an error trying to open file filename. Processing continues. Possible causes are: o The user does not have write access to the subdirectory. o The path specified in the LMU.INI file is incorrect User Response: If the log file specified is on a drive to which LAN Management Utilities/2 has write access, and if the path specified for the file is correct, record the error message and contact IBM Software Support. LMU3503W LMU/2 log error occurred trying to access log file filename Meaning: The LAN Management Utilities/2 log processor has encountered an error trying to access file filename; the log file may have become corrupted. The message being recorded is lost. Processing continues. User Response: Record the error message and contact IBM Software Support. LMU3504W LMU/2 log error occurred trying to read log file filename Meaning: The LAN Management Utilities/2 log processor has encountered an error trying to read from file filename; the log file may have become corrupted. The message being recorded is lost. Processing continues. User Response: Record the error message and contact IBM Software Support. LMU3505W LMU/2 log error occurred trying to time-stamp log file filename Meaning: The LAN Management Utilities/2 log processor has encountered an error trying to time-stamp a record in file filename; the log file may have become corrupted. The message being recorded is lost. Processing continues. User Response: Record the error message and contact IBM Software Support. LMU3506W LMU/2 log error occurred trying to write to log file filename Meaning: The LAN Management Utilities/2 log processor has encountered an error trying to write a record in file filename; the log file may have become corrupted. The message being recorded is lost. Processing continues. User Response: Record the error message and contact IBM Software Support. LMU3507W LMU/2 log error occurred trying to close log file filename Meaning: The LAN Management Utilities/2 log processor has encountered an error trying to close the file filename. The message log is left in an unpredictable state. Processing continues. User Response: Record the error message and contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.20. Numbered Messages (LMU4000 - LMU4999) ΓòÉΓòÉΓòÉ LMU4000E DosScanEnv for environment variable evar failed; rc = returncode Meaning: The LAN Management Utilities/2 relay software (LMURELAY) encountered an unexpected return code returncode from DosScanEnv for environment variable evar; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU4001E NETBIOS {ADD NAME | CALL | RESET | SEND} failed sending output to computername; rc = X'returncode' Meaning: The LAN Management Utilities/2 relay software (LMURELAY) encountered an unexpected return code returncode from the indicated NETBIOS function while sending output to computer computer; processing is terminated. Note that the return code from NETBIOS is hexadecimal. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the NETBIOS NCB return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU4002E Error reading standard input Meaning: The LAN Management Utilities/2 relay software (LMURELAY) encountered an unexpected error reading standard input (STDIN); processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU4003E Invalid option opt Meaning: The LAN Management Utilities/2 relay software (LMURELAY) started with option opt, which is not a valid option; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU4004E Invalid value specified for opt option Meaning: The LAN Management Utilities/2 relay software (LMURELAY) started with an invalid value specified for option opt; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU4005E Required parameter CORRELATOR not specified Meaning: The LAN Management Utilities/2 relay software (LMURELAY) was invoked without required parameter CORRELATOR; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU4006E Invalid value specified for CORRELATOR parameter Meaning: The LAN Management Utilities/2 relay software (LMURELAY) was invoked with an invalid value specified for required parameter CORRELATOR; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU4500E Invalid option opt Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) was invoked with option opt, which is not a valid option; processing is terminated. User Response: See the command format in topic LMUQUERY, correct the command, and reissue LMUQUERY. LMU4501E Invalid parameter parm Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) was invoked with parameter parm, which is not a valid parameter; processing is terminated. User Response: See the command format in topic LMUQUERY, correct the command, and reissue LMUQUERY. LMU4502E Required parameter omitted Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) was invoked without required parameters; processing is terminated. User Response: See the command format in topic LMUQUERY, correct the command, and reissue LMUQUERY. LMU4503E Profile error getting value for required key keyname; rc = returncode Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for the key identified by keyname in the LMU.INI file; processing is terminated. There may be a problem in the LMU.INI file. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. If values were missing, correct the LMU/2 control file. 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU4510I Progname is executing Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) has queried the status of LAN Management Utilities/2 program progname and found that progname is executing in this workstation; processing continues. User Response: None LMU4511W Progname is not executing Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) has queried the status of LAN Management Utilities/2 program progname and found that progname is not executing in this workstation; processing continues. Note: This message is issued if the terminate option was specified and progname is not executing in this workstation. User Response: None LMU4513I Termination signal sent to progname Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) has successfully sent a termination signal to the LAN Management Utilities/2 program progname; processing continues. User Response: None LMU4514W Unable to terminate progname Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) was unable to terminate the LAN Management Utilities/2 program progname; processing continues. User Response: Review previous messages to determine the cause of the error. LMU4520W {DosOpenSem | DosCloseSem} failed for system semaphore semaphore; rc = returncode Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) encountered an unexpected return code returncode from DosOpenSem or DosCloseSem for system semaphore semaphore; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU4521W DosWriteMailslot failed for mailslot mailslot; rc = returncode Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) encountered an unexpected return code returncode from DosWriteMailslot for mailslot mailslot; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU4522W {DosOpenQueue | DosWriteQueue | DosCloseQueue} failed for queue qname; rc = returncode Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) encountered an unexpected return code returncode from DosOpenQueue, DosWriteQueue, or DosCloseQueue for queue qname; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU4523W DosAllocSeg failed; rc = returncode Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) encountered an unexpected return code returncode from DosAllocSeg; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU4524W {DosGiveSeg | DosFreeSeg} failed for selector sel; rc = returncode Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) encountered an unexpected return code returncode from DosGiveSeg or DosFreeSeg for selector sel; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU4525W {DosLoadModule | DosGetProcAddr} failed for {module | function} name; rc = returncode Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) encountered an unexpected return code returncode from DosLoadModule or DosGetProcAddr for name; processing continues. User Response: When returncode is 2, verify that the dynamic link library name is accessable via LIBPATH in CONFIG.SYS. Otherwise, record the information in this message and contact IBM Software Support. LMU4526W DosKillProcess failed for process identifier X'pid'; rc = returncode Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) encountered an unexpected return code returncode from DosKillProcess for process identifier pid; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU4749W DosGetMessage failed for message msgnum in file msgfile; rc = returncode Meaning: The LAN Management Utilities/2 Query software (LMUQUERY) encountered an unexpected return code returncode from DosGetMessage for message number msgnum; processing continues. User Response: When returncode is 2, verify that the message file msgfile is in the current directory or accessable via DPATH. Otherwise, record the information in this message and contact IBM Software Support. LMU4751E Invalid option opt Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) was invoked with option opt, which is not a valid option; processing is terminated. User Response: See the command format in topic APPWATCH, correct the command, and reissue APPWATCH. LMU4752E Invalid value specified for opt option Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) was invoked with an invalid value specified for option opt; processing is terminated. User Response: See the command format in topic APPWATCH, correct the command, and reissue APPWATCH. LMU4753E Profile error getting value for required key keyname; rc = returncode Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for the key identified by keyname in the LMU.INI file; processing is terminated. There may be a problem in the LMU.INI file. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. If values were missing, correct the LMU/2 control file. 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU4755E Error opening file filename Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) encountered an unexpected error opening file filename; processing is terminated. User Response: If the file filename does not exist, reissue APPWATCH with a valid file name. Otherwise, record the information in this message and contact IBM Software support. LMU4756E Error reading file filename Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) encountered an unexpected error reading file filename; processing is terminated. User Response: Record the information in this message and contact IBM Software support. LMU4757W Error closing file filename; rc = returncode Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) encountered an unexpected error closing file filename; processing continues. User Response: Record the information in this message and contact IBM Software support. LMU4758E No valid entires found in file filename Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) detected no valid application entries in file filename; processing is terminated. User Response: Correct the file filename and reissue APPWATCH. LMU4760E Duplicate application appname Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) detected a duplicate application name in file filename. Application names must be unique; processing is terminated. User Response: Correct the file filename and reissue APPWATCH. LMU4761E Insufficeint storage to add appname to application list Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) encountered an error allocating storage to add application appname to application list; processing is terminated; User Response: Terminate applications that are not needed and reissue APPWATCH. LMU4770E DosAllocSeg failed; rc = returncode Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) encountered an unexpected return code returncode from DosAllocSeg; processing is terminated. User Response: Record the information in this message and contact IBM Software support. LMU4771W DosQProcStatus failed; rc = returncode Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) encountered an unexpected return code returncode from DosQProcStatus; processing is terminated. User Response: Record the information in this message and contact IBM Software support. LMU4772E DosSleep failed; rc = returncode Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) encountered an unexpected return code returncode from DosSleep; processing is terminated. User Response: Record the information in this message and contact IBM Software support. LMU4780W Null line detected (line linenum in file filename) Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) detected an null (or blank) line at linenum in file filename; processing continues. User Response: Remove line linenum in file filename. LMU4781E Invalid entry detected (line linenum in file filename) Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) detected an invalid value specified for entry entry on line linenum in file filename; processing is terminated. User Response: Correct line linenum in file filename and reissue APPWATCH. LMU4782W Extraneous text detected (line linenum in file filename) Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) detected an extraneous text on line linenum in file filename; processing continues. User Response: Remove the extraneous text from line linenum in file filename. LMU4790W number instance(s) of appname Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) sends this message in a generic alert to the fault manager whenever the number of instances number of application appname is not within the instance range defined; processing continues. User Response: Contact LAN Administrator. LMU4999W DosGetMessage failed for message msgnum in file msgfile; rc = returncode Meaning: The LAN Management Utilities/2 Application Watch software (APPWATCH) encountered an unexpected return code returncode from DosGetMessage for message number msgnum; processing continues. User Response: When returncode is 2, verify that the message file msgfile is in the current directory or accessable via DPATH. Otherwise, record the information in this message and contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.21. Numbered Messages (LMU5000 - LMU5999) ΓòÉΓòÉΓòÉ LMU5000I PERFCAP data from hh:mm:ss for iiii delivered. Highest rc = returncode Meaning: The data collected from PERFCAP has been placed on the LAN Management Utilities/2 transport for delivery to the managing system database. Each data aggregate is sent separately on the transport at the completion of a collection interval. This message is written to the LAN Management Utilities/2 log file to document the time and highest return code received during the delivery of the data. Variable fields are as follows: o hh:mm:ss - the time of the start of the capture interval o iiii - the length of the capture interval (in seconds) o returncode - the highest return code received from the transport User Response: This message is informational only. It should be received at the end of every capture interval. Note that the message placed in the LAN Management Utilities/2 log file is time-dated. This time-stamp documents the time at which the data delivery to the transport took place. LMU5001W SPM/2 system pipe error (rc = returncode) from applid. A capture interval is bypassed. Meaning: The IBM System Performance Monitor/2 (SPM/2) system pipe is necessary for the application to start and control data collection. Possible causes are: o Another application is holding the SPM/2 system pipe. o SPM/2 is not installed on this workstation. Variable fields are as follows: o returncode - the return code received from the last attempt to open the system pipe. o applid - the application which received the error (PERFCAP or PERFWACH). User Response: If SPM/2 is not installed, you must install it on the workstation intended to execute PERFCAP or PERFWACH. Otherwise, there is another application using the SPM/2 system. Coordinate usage of the system pipe with other application users. As a result of receiving this message, the application has bypassed the current capture interval. At the expiration of the frequency interval, the application will try again. LMU5002E applname aggregate exhausted. cnt type records lost. Meaning: The application identified by applname has exhausted an internal data area. As a result, trace records from IBM System Performance Monitor/2 (SPM/2) were lost. cnt and type indicate the number and type of trace records that were lost in the capture interval. User Response: Record the error message and contact IBM service. LMU5003W inikey = inival is in error; value ignored. Meaning: A performance threshold value for PERFWACH, OSRWATCH, or SRVWATCH is in error in the LMU.INI file. The LMU.INI file key (inikey) indicates which application and threshold; inival is the erroneous value. User Response: Consult Management Applications (OS/2) for the threshold values allowed by the LMU/2 performance application that was in use. Correct the value in the LMU/2 control file, then rebuild the LMU.INI file by running the LINI program with the modified LMU/2 control file as input. LMU5004E Error opening watch log filespec. Application terminated. Meaning: The watch log named by filespec could not be opened. Possible causes are: o The user does not have write access to the subdirectory. o The user does not have enough disk space to create the watch log file. User Response: Correct the problem with the file identified by filespec and reissue the command, or provide a different file specification on the command. LMU5005E Invalid parameter: parm Meaning: An invalid parameter (parm) was specified on the performance command issued. User Response: Consult Management Applications or the command help to determine valid parameters for the performance application. LMU5006E Invalid parameter value: pval Meaning: The performance command that was entered contained a parameter value (pval) that is outside the range for a numeric or percentage value. Valid values are: o 1 - 32767 for a numeric parameter o 1 - 99 for a percentage parameter. User Response: Correct the command specification and resubmit the command. LMU5007W Error creating type generic alert (rc = returncode). Meaning: An error occurred while trying to forward the generic alert indicated by type. A return code of 8 typically indicates that AUEPITCH is not executing on the workstation generating the alert. User Response: If returncode is 8, ensure that AUEPITCH is executing on the workstation. If returncode has some other value, record the message and contact IBM service. LMU5008W Mask value char is invalid and ignored. Meaning: The IBM System Performance Monitor/2 control mask value indicated by char is not valid. The erroneous mask value is bypassed and processing continues. The mask values specified on the /m option of PERFCAP or PERFWACH must be one or a mixture of the following: o c - for process data. o p - for physical disk data. o l - for logical disk data. o r - for RAM memory data. o s - for swap data. User Response: If necessary, terminate the performance application (PERFCAP or PERFWACH), correct the value for /m, and resubmit the command. LMU5013W INI parm keyname = value is in error, value ignored. Meaning: OSRWATCH or SRVWATCH encountered an invalid setting value for threshold parameter keyname in the LMU.INI file, and used the default value of 0 for the threshold. The value specified is of the wrong size, or contains incorrect characters for the kind of information required, or is outside the allowable range for the parameter. User Response: Check the requirements for the parameter value, correct the value in the LMU/2 control file, and recreate the LMU.INI file. LMU5101I PROC active > pp% procname at aa.a% Meaning: The execution time of a process exceeds the threshold during the capture interval. Variable fields are as follows: o pp - the PROC threshold value (percentage) in use. This is a percentage of the time available to all processes during the capture interval. o procname - the process name of the offending process. If the process name is not available, the format of this field is `pid 0xxx' where 0xxx is the process ID of the offending process. o aa.a - the calculated percentage of execution time for the offending process. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5102I DISK active > pp% ttt.tttt,iiii Meaning: The execution time for disk activity exceeds the threshold percentage over the capture interval. Variable fields are as follows: o pp - the DISK threshold value in use o ttt.tttt - the actual execution time (in seconds) of the disk activity o iiii - the interval period that was monitored. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5103I SWAP active > pp% ttt.tttt,iiii Meaning: The execution time for swap activity exceeds the threshold percentage over the capture interval. Variable fields are as follows: o pp - the SWAP threshold value in use o ttt.tttt - the actual execution time (in seconds) of the swap activity o iiii - the interval period that was monitored. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5104I FREE memory < pp% ffffffff,aaaaaaaa Meaning: The free memory in the workstation has fallen below the threshold percentage of the total available memory (memory available for swapping). Variable fields are as follows: o pp - the FREE threshold value in use o ffffffff - the amount of free memory available o aaaaaaaa - the amount of memory available for swapping. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5105I TCPU active > pp% - aaaaaaaa Meaning: The central processing unit (CPU) utilization in the workstation has exceeded the threshold percentage of total CPU utilization. Variable fields are as follows: o pp - the CPU utilization threshold value in use o aaaaaaaa - the amount of CPU utilization encountered. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5201I NCBS at nnnnnnnn < thr% aaa,mmm Meaning: The count of available NCBs has fallen below the specified threshold percentage. Variable fields are as follows: o nnnnnnnn - the requester ID of the workstation where the condition was detected o thr - the specified threshold value that created the condition exception o aaa - the actual number of NCBs that are available o mmm - the defined maximum number of NCBs. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-defined alerts control table at the fault manager. Refer to User-Defined Table for a description of the alert control table. LMU5202I NSES at nnnnnnnn < thr% aaa,mmm Meaning: The count of available NETBIOS sessions has fallen below the specified threshold percentage. Variable fields are as follows: o nnnnnnnn - the requester ID of the workstation where the condition was detected o thr - the specified threshold value that created the condition exception o aaa - the actual number of NETBIOS sessions that are available o mmm - the defined maximum number of sessions. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-defined alerts control table at the fault fanager . Refer to User-Defined Table for a description of the alert control table. LMU5203I NERR at nnnnnnnn >= thr typ,aaa Meaning: The count of packet errors is greater than or equal to the specified threshold count. Variable fields are as follows: o nnnnnnnn - the requester ID of the workstation where the condition was detected o thr - the specified threshold value that created the condition exception o typ - the error type (RCV or XMT) o aaa - the actual number of transmit or receive errors that were detected. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-defined alerts control table at the fault manager. Refer to User-Defined Table for a description of the alert control table. LMU5204I NABT at nnnnnnnn >= thr typ,aaa Meaning: The count of aborted transmissions is greater than or equal to the specified threshold count. Variable fields are as follows: o nnnnnnnn - the requester ID of the workstation where the condition was detected o thr - the specified threshold value that created the condition exception o typ - the error type (ABT) o aaa - the actual number of aborted transmissions that were detected. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the alert control table at the fault manager. Refer to User-Defined Table for a description of the alert control table. LMU5205I NDTO at nnnnnnnn >= thr typ,aaa Meaning: The count of DLC timeout errors is greater than or equal to te specified threshold count. Variable fields are as follows: o nnnnnnnn - the requester ID of the workstation where the condition was detected o thr - the specified threshold value that created the condition exception o typ - the error type (T1 or Ti ) o aaa - the actual number of DLC timeouts that were detected. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the alert control table at the fault manager. Refer to User-Defined Table for a description of the alert control table. LMU5206I NLGN at nnnnnnnn >= thr aaa Meaning: The count of users logged on to the server is greater than or equal to the specified threshold count. Variable fields are as follows: o nnnnnnnn - the server ID of the workstation supporting the logons o thr - the specified threshold value that created the condition exception o aaa - the actual number of users logged on to the server. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the alert control table at the fault manager. Refer to User-Defined Table for a description of the alert control table. LMU5207I NBFX at nnnnnnnn >= thr typ,aaa Meaning: The count of buffer exhaustions is greater than or equal to te specified threshold count. Variable fields are as follows: o nnnnnnnn - the requester ID of the workstation where the condition was detected o thr - the specified threshold value that created the condition exception o typ - the buffer type (RCV or XMT) o aaa - the actual number of times an adapter buffer was needed and could not be obtained. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the alert control table at the fault manager. Refer to User-Defined Table for a description of the alert control table. LMU5208I NDTI at nnnnnnnn >= thr typ,aaa Meaning: The count of DLC inactivity timeout errors is greater than or equal to the specified threshold count. Variable fields are as follows: o nnnnnnnn - the requester ID of the workstation where the condition was detected o thr - the specified threshold value that created the condition exception o typ - the error type (Ti, for inactivity) o aaa - the actual number of DLC inactivity timeouts that were detected. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the alert control table at the fault manager. Refer to User-Defined Table for a description of the alert control table. LMU5209I NDT1 at nnnnnnnn >= thr typ,aaa Meaning: The count of DLC response timeout errors is greater than or equal to the specified threshold count. Variable fields are as follows: o nnnnnnnn - the requester ID of the workstation where the condition was detected o thr - the specified threshold value that created the condition exception o typ - the error type (T1, for response) o aaa - the actual number of DLC response timeouts that were detected. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the alert control table at the fault manager. Refer to User-Defined Table for a description of the alert control table. LMU5250E OSRWATCH NCB.RESET error rc = returncode(Hex). Status collection terminated. Meaning: The OSRWATCH utility has encountered an error issuing the NCB.RESET command; processing is terminated. OSRWATCH requires one session, one command and one name. If returncode is 38, there may be a shortage of one of these resources; the shortage may be temporary. User Response: If the return code is 38, try OSRWATCH later. If you still get this message with a return code of 38: 1. Compare the NETBIOS resources requested by the OS/2 LAN Requester (the net1 = statement in IBMLAN.INI) to the NETBIOS resource allocation in the LAN Feature Profile (NETBIOS) in OS/2 Communications Manager. If the NETBIOS resources indicated in the IBMLAN.INI file equal or exceed the resources allocated by Communications Manager, go to the next step; otherwise, contact IBM Software Support. 2. Increase the maximum number of sessions, commands, or names (as applicable) in your Communications Manager LAN Feature Profile (NETBIOS) to insure that at least one session, one command, and one name are available to applications other than the OS/2 LAN Requester. 3. Restart the computer and try OSRWATCH again. If the problem still exists, contact IBM Software Support with the error message information. If the return code is not 38, and if you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU5251E NetLogonEnum return code: returncode Meaning: OSRWATCH has encountered an error obtaining the list of computer names to monitor; processing is terminated. User Response: Record the information in this message and contact IBM suppport. LMU5301W NetWkstaGetInfo return code: rc. Meaning: An error occurred while attempting to determine the station's ID and the name of the station's server. User Response: Document the message and contact IBM Software Support. LMU5302E Userid logonid is not admin at server msname Meaning: SRVWATCH was issued from a workstation by a userid that is not defined in OS/2 User Profile Management (UPM) as an administrator to the server identified by msname; processing is terminated. User Response: Do one of the following: o Change SRVWATCH to specify a server (/s option) to which this workstation is defined as an administrator o Change the UPM definition at msname to specify this workstation as an administrator. Then reissue the command. LMU5303W NetStatisticsGet2 return code: rc. Meaning: An error occurred while attempting to obtain the designated server's statistics. If the return code is 53, the server cannot be located (it may have been specified incorrectly in the SRVWATCH command). User Response: See SRVWATCH to verify the command format, ensure that your SRVWATCH command correctly identifies the server, and resubmit the command. If this does not correct the problem, document the message and contact IBM Software Support. LMU5306E Invalid parameter value: pval Meaning: An invalid parameter value pval was specified on the SRVWATCH command. The parameter value must be within the range of 0 - 60000. User Response: Correct the command specification and resubmit the command. LMU5310I SAVR at servname > ms,cnt avr Meaning: The server average response time exceeded the threshold value in cnt consecutive collections. Variable fields are as follows: o servname - the name of the server from which the data was collected o ms - the average response time threshold value in milliseconds o cnt - the number of consecutive capture intervals in which the response time threshold was exceeded o avr - the average response time over the cnt collection periods, which resulted in this alert. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5311I SRBF at servname >= cnt, actual actual Meaning: The number of regular buffer allocation failures in a statistics collection is greater than or equal to the threshold specification for regular buffers. Variable fields are as follows: o servname - the name of the server from which the data was collected o cnt - the regular buffer allocation failure threshold value o actual - the reported number of regular buffer allocation failures. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. Note: Regularly occurring buffer allocation failures indicate that the parameters of the server may need adjustment. LMU5312I SBBF at servname >= cnt, actual actual Meaning: The number of big buffer allocation failures in a statistics collection is greater than or equal to the threshold specification for big buffers. Variable fields are as follows: o servname - the name of the server from which the data was collected o cnt - the big buffer allocation failure threshold value o actual - the reported number of big buffer allocation failures. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. Note: Big buffer allocation failures indicate that the parameters of the server may need adjustment. LMU5313I TSES at servname >= cnt, actual actual Meaning: The number of total sessions in a statistics collection is greater than or equal to the threshold specification for total sessions. Variable fields are as follows: o servname - the name of the server from which the data was collected o cnt - the total sessions threshold value o actual - the reported number sessions. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5314I TCON at servname >= cnt, actual actual Meaning: The number of total connections in a statistics collection is greater than or equal to the threshold specification for total connections. Variable fields are as follows: o servname - the name of the server from which the data was collected o cnt - the total connection threshold value o actual - the reported number of connections. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5315I TOPN at servname >= cnt, actual actual Meaning: The number of total file opens in a statistics collection is greater than or equal to the threshold specification for file opens at the server. Variable fields are as follows: o servname - the name of the server from which the data was collected o cnt - the total file opens threshold value o actual - the reported number of file opens. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5316I SSES at reqsname >= cnt, actual actual Meaning: The number of individual user sessions with a requester during a statistics collection is greater than or equal to the threshold specification for individual user sessions at the server. Variable fields are as follows: o reqsname - the name of the requester about which the data was collected o cnt - the total individual user sessions threshold value o actual - the reported number of user sessions with the requester. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5317I SCON at reqsname >= cnt, actual actual Meaning: The number of individual user connections with a requester during a statistics collection is greater than or equal to the threshold specification for individual user connections at the server. Variable fields are as follows: o reqsname - the name of the requester about which the data was collected o cnt - the total individual user connections threshold value o actual - the reported number of user connections with the requester. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5318I SOPN at reqsname >= cnt, actual actual Meaning: The number of individual user file opens at the server from a requester during a statistics collection is greater than or equal to the threshold specification for individual file opens at the server. Variable fields are as follows: o reqsname - the name of the requester about which the data was collected o cnt - the total individual user file opens threshold value o actual - the reported number of user file opens at the server. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. LMU5319I SIDL at reqsname >= cnt, actual actual Meaning: The amount of individual session idle time for a requester during a statistics collection is greater than or equal to the threshold specification for individual session idle time at the server. Variable fields are as follows: o reqsname - the name of the requester about which the data was collected o cnt - the individual session idle time threshold value o actual - the reported amount of session idle time for the requester. User Response: This message is provided as the user data portion of a generic alert sent to the fault manager. Responses to the alert should be controlled by the user-written alert-processing table at the fault manager. Refer to User-Defined Table for a description of the user-written table. ΓòÉΓòÉΓòÉ 21.22. Numbered Messages (LMU6000 - LMU6999) ΓòÉΓòÉΓòÉ LMU6000W Codepoint X'codept' for data type was not recognized. Meaning: QUERYVPD or QDOSVPD does not recognize the code point codept returned by the computer for the object identified by data type. User Response: Document this code point and report it to your service organization. An upgrade or maintenance may be necessary. LMU6001E parameter is a required parameter with the option option. Meaning: The option selected (option) must be a accompanied by a specification for parameter. User Response: Review the QUERYVPD or QDOSVPD program help panel to obtain the correct syntax and try the command again. Execution of the program is terminated. LMU6002E This machine is not recognized by progname. Model = codepoint1, submodel = codepoint2. Meaning: The QUERYVPD or QDOSVPD program (identified by progname) does not recognize this machine. User Response: Check the hardware requirements in Introduction to see if this machine is supported. If so, document this code point and report it to your service organization. Maintenance may be necessary. LMU6004W opt is an unrecognized option. Option ignored. Meaning: The option identified by opt was specified for QUERYVPD or QDOSVPD but is not a recognized option. The option is ignored and the program continues execution. User Response: Review the program help panel for a list of the valid options. LMU6005E Destination specifying of managing system with database is too long (21 characters max.). Meaning: The computer name or internetwork address entered on the /r option is greater than 21 characters. The program is terminated. User Response: Correct the specification of computer name or internetwork address on the /r option so that the name of the managing system with database is within the 21 character limit. LMU6009E Redirection to file filespec was unsuccessful. Meaning: The user requested that the console display of QUERYVPD or QDOSVPD be directed to the location identified by filespec. The redirection could not be completed. Possible causes are: o Nonexistent subdirectory o Nonexistent drive o Write-protected disk o File name too long or contains invalid characters. User Response: Ensure that: o The output is directed to a valid drive, subdirectory, and file name. o The disk is not write-protected. The user may specify a file name in the current directory, or, using a full drive:\path\filename specification, a location outside the current directory. LMU6010I Progname output has been successfully redirected to the file filespec. Meaning: The user requested that the output of QUERYVPD or QDOSVPD be redirected to filespec. The file was successfully opened and the console display will be redirected to the filespec. User Response: None. LMU6011I Transport of data to the managing system with database was successful. Meaning: The user requested that the output of the QUERYVPD or QDOSVPD program be redirected to the managing system with database. If the program was QDOSVPD, the data was sent to the destination identified in the /r option. If the program was QUERYVPD.EXE, the data was sent to the destination identified in the /r option, if any destination was named; otherwise, the data was sent to the destination identified in the LMU.INI file as MANAGING_SYSTEM_WITH_DATABASE. If the program was QUERYVPD.NLM, the data was sent to the destination identified in the /r option, if any destination was named; otherwise, the data was sent to the destination identified in the bindery as MANAGING_SYSTEM_WITH_DATABASE. User Response: None. LMU6012E Transport of data to the managing system with database failed. Refer to the LMU/2 message log for additional information. Meaning: Although the gathering of vital product data was successful, the data could not be delivered to the managing system with database. If the program was QDOSVPD, the destination was identified in the /r option. If the program was QUERYVPD.EXE, the destination was identified in the /r option, if any destination was named; otherwise, the destination was identified in the LMU.INI file as MANAGING_SYSTEM_WITH_DATABASE. If the program was QUERYVPD.NLM, the data was sent to the destination identified in the /r option, if any destination was named; otherwise, the destination was identified in the bindery as MANAGING_SYSTEM_WITH_DATABASE. User Response: Refer to the LAN Management Utilities/2 message log for a related error message to determine the true cause of the failed delivery of data. LMU6016W Micro Channel adapter ID X'codepoint' is not recognized. Meaning: The Micro Channel* adapter ID codepoint was not recognized by the QUERYVPD or QDOSVPD program. User Response: Use the ADAPTERS.DEF file to define the adapter ID and description to the program. Refer to ADAPTERS.DEF for more information on defining adapters. Note: Only the QDOSVPD and QUERYVPD.EXE programs read the ADAPTERS.DEF file. LMU6018E The product number could not be determined. Machine number X'codepoint', Disk Size megabytes. Meaning: The product number of this machine was not recognized by the QUERYVPD or QDOSVPD program. User Response: Document this code point and report it to your service organization. Maintenance may be necessary. LMU6019E Allocation of nn bytes failed. Meaning: There is not enough free memory in the machine to run the QUERYVPD or QDOSVPD program. The program is terminated. User Response: Free some memory in the machine and rerun the program. LMU6020E Dynamic load of program.DLL failed; rc = rc. Meaning: QUERYVPD attempted to dynamically load a dynamic link library (program.DLL) that is required for the successful execution of the program. QUERYVPD is terminated. User Response: Refer to the Installation and Customization section to ensure that the program is installed correctly. LMU6021E Dynamic load of procedure procedure within program.DLL failed; rc = rc. Meaning: QUERYVPD attempted to dynamically load a procedure (procedure) within the dynamic link library (program.DLL) that is required for the successful execution of the program. QUERYVPD is terminated. User Response: Refer to the Installation and Customization section to ensure that the program is installed correctly. LMU6022I Vital product data was loaded successfully from path. Meaning: QUERYVPD.NLM successfully located and loaded the previously saved vital product data from the directory specified by path. User Response: None. LMU6023E Execution terminated. Meaning: Program execution has been terminated. User Response: Refer to the messages preceeding this one to determine the reason for premature program termination. LMU6024E Loading of vital product data from path failed. Meaning: QUERYVPD.NLM attempted to locate the previously saved QDOSVPD vital product data from the directory specified by path, but either the file was not present or the contents were determined to be invalid. User Response: Ensure that the directory pointed to by path specifies the directory containing the previously saved vital product data (Q$V$P$D.SAV). If path specifies a directory in the DOS partition (C:\, for example),: o Check that the path specified with the /I option on the QUERYVPD.NLM command matches the path specified in the /K option on the QDOSVPD command that was used to collect and store the vital product data. If the /I option was not used, use LMULOAD.NLM to check the path specified for LMU2 DOS DIRECTORY in the bindery. It may be neccessary to shut down NetWare and return to the DOS environment to rerun QDOSVPD. If path specifies a directory in the Netware partition (eg. SYS:\LMU2\): o Check that the path specified with the /W option on the QUERYVPD.NLM command matches the path specified in the /K option on the QDOSVPD command that was used to collect and store the vital product data. or for LMU2 INSTALL DIRECTORY (via LMULOAD). If the /W option was not used, use LMULOAD.NLM to check the path specified for LMU2 INSTALL DIRECTORY in the bindery. It may be neccessary to restore DOS to the environment and rerun QDOSVPD, then QUERYVPD, ensuring that the /I option or LMU2 DOS DIRECTORY point to the appropriate path in the DOS partition or that the /W option or LMU2 INSTALL DIRECTORY point to the appropriate path in the NetWare partition. LMU6025E Invalid type definition detected on line linenum of file filespec. Meaning: QUERYVPD or QDOSVPD encountered an error while parsing the line identified by linenum in the definition file identified by filespec. Parsing of the file is terminated. User Response: Refer to the section of this document that describes the correct format and rules governing the defintion file identified by type. Correct the error and rerun the program. LMU6026E Program has run out of memory collecting data. Meaning: QUERYVPD or QDOSVPD exceeded the 64K data or work block allocated for collecting vital product data. Execution of the program is terminated. User Response: Selectively turn off the inclusion of user data, critical file searching, or syslevel processing to reduce the total memory required. If the problem persists, call your IBM service representative. LMU6027I Vital product data successfully saved in path. Meaning: QUERYVPD or QDOSVPD has successfully saved the vital product data in the directory specified by path. QDOSVPD saved the vital product data in the DOS directory specified by path for future use by QUERYVPD.NLM. QUERYVPD.NLM saved the vital product data in the NetWare directory specified by path for future use by QUERYVPD.NLM when DOS has been removed from the system. User Response: Note the directory pointed to by path for future use with these commands. LMU6028E Vital product data file could not be found. Meaning: QUERYVPD attempted to locate the previously saved vital product data but the search failed because the user did not specify a location for the program to find it. User Response: Use command line options (/Ipath or /Wpath) or customization routine (LMULOAD.NLM, parameters LMU2 DOS DIRECTORY or LMU2 INSTALL DIRECTORY) to specify the path of the directory containing the previously saved vital product data (Q$V$P$D.SAV). LMU6029I Saving of vital product data in path failed. Meaning: QUERYVPD or QDOSVPD attempted to save vital product data in the directory specified by path but the operation failed. User Response: Ensure that the directory pointed to by path specifies a valid directory name, access is available, and space is available. LMU6030E Type table (filename) could not be found. Meaning: QUERYVPD or QDOSVPD attempted to locate the table identified by type and named filename, containing all the system-provided type IDs and descriptions. The program is terminated. User Response: Review the program search algorithms to ensure that filename is available to the program. Otherwise, use the /W command line option to specifiy the path of the directory containing filename. Rerun the program. ΓòÉΓòÉΓòÉ 21.23. Numbered Messages (LMU7000 - LMU7999) ΓòÉΓòÉΓòÉ LMU7000E Invalid option opt Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) was invoked with option opt, which is not a valid option; processing is terminated. User Response: See the command format in topic IPXWATCH, correct the command, and reissue IPXWATCH. LMU7001E Invalid value specified for opt option Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) was invoked with an invalid value specified for option opt; processing is terminated. User Response: See the command format in topic IPXWATCH, correct the command, and reissue IPXWATCH. LMU7010I IPX Version version Revision revision Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) displays the version version and revision level revision of the installed IPX driver. User Response: None. LMU7020W {IpxGetVersion | IpxGetStatistics} failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) encountered an unexpected return code returncode from IpxGetVersion or IpxGetStatistices; processing continues. User Response: Record the information in this message and contact IBM Software support. LMU7030E DosSleep failed; rc = returncode Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) encountered an unexpected return code returncode from DosSleep; processing is terminated. User Response: Record the information in this message and contact IBM Software support. LMU7040W CFRF at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the cumulative find route failures value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7041W CIPC at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the cumulative ignored packet count value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7042W CMPC at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the cumulative malformed packet count value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7043W COSF at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the cumulative open socket fauilues value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7044W CRPC at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the cumulative receive packet count value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7045W CSPC at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the cumulative send packet count value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7050W DFRF at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the delta find route failures value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7051W DIPC at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the delta ignored packet count value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7052W DMPC at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the delta malformed packet count value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7053W DOSF at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the delta open socket failures value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7054W DRPC at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the delta receive packet count value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7055W DSPC at value >= threshold Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) sends this message in a generic alert to the fault manager whenever the delta send packet count value equals or exceeds the specified threshold threshold; processing continues. User Response: Contact LAN Administrator. LMU7149W DosGetMessage failed for message msgnum in file msgfile; rc = returncode Meaning: The LAN Management Utilities/2 IPX Watch software (IPXWATCH) encountered an unexpected return code returncode from DosGetMessage for message number msgnum; processing continues. User Response: When returncode is 2, verify that the message file msgfile is in the current directory or accessable via DPATH. Otherwise, record the information in this message and contact IBM Software Support. LMU7150E NWRWATCH cannot be run in OS/2 mode Meaning: The LAN Management Utilities/2 NetWare Requester Watch software (NWRWATCH) is a DOS only application and cannot be invoked from an OS/2 window, OS/2 full screen session, or OS/2 DOS box; processing is terminated. User Response: See the command format in topic NWRWATCH, correct the command, and reissue NWRWATCH on a DOS workstation. LMU7151E Invalid option opt Meaning: The LAN Management Utilities/2 NetWare Requester Watch software (NWRWATCH) was invoked with option opt, which is not a valid option; processing is terminated. User Response: See the command format in topic NWRWATCH, correct the command, and reissue NWRWATCH. LMU7152E Invalid value specified for opt option Meaning: The LAN Management Utilities/2 NetWare Requester Watch software (NWRWATCH) was invoked with an invalid value specified for option opt; processing is terminated. User Response: See the command format in topic NWRWATCH, correct the command, and reissue NWRWATCH. LMU7160E IpxInitialize failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 NetWare Requester Watch software (NWRWATCH) encountered an unexpected return code returncode from IpxInitialize; processing is terminated. User Response: Record the information in this message and contact IBM Software support. LMU7161W {GetInternetAddress | GetConnectionInformation} failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 NetWare Requester Watch software (NWRWATCH) encountered an unexpected return code returncode from GetInternetAddress or GetConnectionInformation; processing continues. User Response: Record the information in this message and contact IBM Software support. LMU7162W {BeginDiagnostics | EndDiagnostics | GetIPXStatistics | GetSPXStatistics} for computername failed; {completion code | rc} = X'returncode' Meaning: The LAN Management Utilities/2 NetWare Requester Watch software (NWRWATCH) encountered an unexpected return code returncode from BeginDiagnostics, EndDiagnostics, GetIPXStatistics, or GetSPXStatistics; processing continues. User Response: Record the information in this message and contact IBM Software support. LMU7170E DosSleep failed; rc = returncode Meaning: The LAN Management Utilities/2 NetWare Requester Watch software (NWRWATCH) encountered an unexpected return code returncode from DosSleep; processing is terminated. User Response: Record the information in this message and contact IBM Software support. LMU7171W thresname at value >= threshold for computername Meaning: The LAN Management Utilities/2 NetWare Requester Watch software (NWRWATCH) has detected an alertable condition (value equals or exceeds the specified threshold threshold) for thresname on workstation computername; processing continues. NWRWATCH sends a generic alert (message LMU7180W-LMU7206W) to the fault manager to report this condition. User Response: Contact LAN Administrator. LMU7299W DosGetMessage failed for message msgnum in file msgfile; rc = returncode Meaning: The LAN Management Utilities/2 NetWare Requester Watch software (NWRWATCH) encountered and unexpected return code returncode from DosGetMessage; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU7300E Invalid option opt Meaning: The LAN Management Utilities/2 DOS Heartbeat software (LMUDOSHB) was invoked with option opt, which is not a valid option; processing is terminated. User Response: See the command format in topic LMUDOSHB, correct the command, and reissue LMUDOSHB. LMU7301E Invalid value specified for opt option Meaning: The LAN Management Utilities/2 DOS Heartbeat software (LMUDOSHB) was invoked with an invalid value specified for option opt; processing is terminated. User Response: See the command format in topic LMUDOSHB, correct the command, and reissue LMUDOSHB. LMU7302E Required parameter MANAGING-SYSTEM not specified Meaning: The LAN Management Utilities/2 DOS Heartbeat software (LMUDOSHB) was invoked without specifying the target managing system; processing is terminated. User Response: See the command format in topic LMUDOSHB, correct the command, and reissue LMUDOSHB. LMU7303E Invalid value specified for MANAGING-SYSTEM parameter Meaning: The LAN Management Utilities/2 DOS Heartbeat software (LMUDOSHB) was invoked with an invalid value specified for the target managing system; processing is terminated. User Response: See the command format in topic LMUDOSHB, correct the command, and reissue LMUDOSHB. LMU7310E Error sending heartbeat to managing system msname; rc = returncode Meaning: The LAN Management Utilities/2 DOS Heartbeat software (LMUDOSHB) encountered an unexpected return code returncode from LMUSEND while attempting to send heartbeat to msname; processing is terminated. User Response: Check the LMU/2 log for additional messages to determine the cause of the error. LMU7399W DosGetMessage failed for message msgnum in file msgfile; rc = returncode Meaning: The LAN Management Utilities/2 DOS Heartbeat software (LMUDOSHB) encountered and unexpected return code returncode from DosGetMessage; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU7905E LMUGUI is already executing Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) is already executing on this workstation; processing is terminated. User Response: None LMU7907E Insufficient storage to allocate stack for tname thread Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected error while attempting to allocate a stack for the thread named tname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU7920E {DosLoadModule | DosGetProcAddr} failed for {module | function} name; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from DosLoadModule or DosGetProcAddr for name while sending output to computer computer; processing is terminated. Possible causes for DosLoadModule include the following: o OS/2 LAN Requester or NetWare Requester for OS/2 is not installed o Missing LIBPATH specification in CONFIG.SYS. User Response: For DosLoadModule, install the required software and/or update LIBPATH statement in CONFIG.SYS; reboot, then reissue LMUCMD. Otherwise, record the information in this message and contact IBM Software Support. LMU7940W Invalid data received; data discarded Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) has received invalid data. The data is discarded; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU7942I Termination request received from computername Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) has received an LMUQUERY request from computername to terminate. User Response: None LMU7943W Invalid request (type xxxx) received from computername; request discarded Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) has received a type xxxx request, which is invalid, from computer computername. The request is discarded; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU7950E {DosCreateThread | DosSetPrty |DosExitList} failed for tname thread; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from DosCreateThread, DosSetPrty, or DosExitList for thread tname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU7951E {DosCreateQueue | DosOpenQueue | DosWriteQueue | DosReadQueue | DosCloseQueue} failed for queue qname; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from DosCreateQueue, DosOpenQueue, DosWriteQueue, DosReadQueue, or DosCloseQueue for queue qname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU7952E Insufficient storage to allocate work area for tname thread Meaning: The LAN Management Utilities/2 Graphical User Interface (LMUGUI) encountered an unexpected error while allocating a work area for thread tname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU7953W Insufficient storage to process data from tname thread; data discarded Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected error while allocating a buffer for data received by thread tname; processing continues but the data is discarded. User Response: Record the information in this message and contact IBM Software Support. LMU7954E Profile error getting value for required key keyname; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for the key identified by keyname in the LMU.INI file; processing is terminated. There may be a problem in the LMU.INI file. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. If values were missing, correct the LMU/2 control file. 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU7955W Profile error getting value for key keyname; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for the key identified by keyname in the LMU.INI file; processing continues. There may be a problem in the LMU.INI file. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. If values were missing, correct the LMU/2 control file. 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU7956W DosFreeSeg failed for selector sel; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from DosFreeSeg for selector sel; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU7957E {DosCreateSem | DosCloseSem} failed for system semaphore semaphore; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from DosCreateSem or DosCloseSem for system semaphore semaphore; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU7961E {SpxOpenSocket | SpxCloseSocket} failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from the indicated SPX function; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU7962W DosSemWait for {SpxListenForConnection | SpxListenForConnectionPacket | SpxTerminateConnection} failed; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from DosSemWait for the indicated SPX function; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU7963W {SpxECBErrorCheck | SpxListenForConnection | SpxGetConnectionStatus | SpxListenForConnectionPacket | SpxTerminateConnection} failed; {rc | status}%2 = X'code' Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code or status code from the indicated SPX function; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU7965W Invalid SPX packet received from computername; data discarded Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) has received an invalid SPX packet from computername; processing continues but the data is discarded. User Response: Record the information in this message and contact IBM Software Support. LMU7966W SPX packet sequence number error detected on connection with computername; data discarded Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) has detected a packet sequence error on connection with computername; processing continues but the data is discarded. User Response: Record the information in this message and contact IBM Software Support. LMU7967W Insufficient space to receive SPX packet from computername; data discarded Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) has received an SPX packet that would make the current data request too large; processing continues but the data is discarded. User Response: Record the information in this message and contact IBM Software Support. LMU7988E Unable to send alert to LMUGUI Meaning: The LAN Management Utilities/2 Graphical User Interface Alert Forwarding software (LMUGUICM) was unable to send an alert to the LAN Management Utilities/2 Graphical User Interface software (LMUGUI); processing continues but the data is discarded. User Response: Insure that the LAN Management Utilities/2 Graphical User Interface software (LMUGUI) is executing. If this situation continues after starting LMUGUI, record the information in this message and contact IBM Software Support. LMU7989E Required parameter(s) omitted Meaning: The LAN Management Utilities/2 Graphical User Interface Alert Forwarding command (LMUGUICM) was not issued with all of the required parameters. User Response: Insure that the both the computername and the message text were entered with the LMUGUICM command. If the command was submitted correctly, record the information in this message and contact IBM Software Support. LMU7990E Unable to load LMUGUIWN.DLL Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code from DosLoadModule while loading the DLL containing the LMUGUI dialog boxes. Possible cause for this error is a missing LIBPATH specification in CONFIG.SYS. User Response: If LMUGUIWN.DLL is not in a directory that is listed in the LIBPATH statement, update the LIBPATH statement in CONFIG.SYS; reboot, then reissue LMUGUI. Otherwise, record the information in this message and contact IBM Software Support. LMU7991E Unable to start LmuGui transport threads Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected error while attempting to start its communication threads. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU7992E Unable to load window resources for LMUGUI.EXE Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an error while initiating the Presentation Manager resources required by LMUGUI; processing is terminated. Possible causes could be lack of memory or harddisk space. User Response: If the workstation is not experiencing hardware problems, record the information in this message and contact IBM Software Support. LMU7993E DosStartSession failed; rc = X'%3' Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) has received an unexpected return code from DosStartSession while attempting to execute a command. User Response: Retry the command. If it continues to fail, record the information in this message and contact IBM Software Support. LMU7995E {NCB.RESET | NCB.ADD.NAME} for adapter adpnum failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from the indicated NETBIOS function using adapter adpnum; processing is terminated. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the NETBIOS return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU7996W {NCB.LISTEN | NCB.RECEIVE | NCB.HANG.UP} for adapter adpnum failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from the indicated NETBIOS function using adapter adpnum; processing continues. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the NETBIOS return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU7997W DosAllocSeg failed for nbytes bytes; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from DosAllocSeg attempting to allocate nbytes; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU7998W DosReadQueue failed for queue qname; rc = returncode Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) encountered an unexpected return code returncode from DosReadQueue for queue qname; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU7999W Invalid inquiry request (type xxxx) received from computername Meaning: The LAN Management Utilities/2 Graphical User Interface software (LMUGUI) has received type xxxx inquiry request, which is invalid, from computer computername. The inquiry request is discarded; processing continues. User Response: Record the information in this message and contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.24. Numbered Messages (LMU8000 - LMU8999) ΓòÉΓòÉΓòÉ LMU8001E SHUTDOWN cannot be run on this version of OS/2 Meaning: SHUTDOWN was issued for this machine, but the level of OS/2 is unsupported. User Response: To run SHUTDOWN on the machine, install a supported level of OS/2. See topic Hardware and Software Requirements for the software requirements. LMU8002E Opt is an unrecognized option. Meaning: The SHUTDOWN command was issued for this machine, but the option on the SHUTDOWN command is neither ? nor /b. Only options /b and ? are valid. SHUTDOWN was not executed. User Response: To execute SHUTDOWN on this machine, the user who issued the command should correct the command and try again. LMU8003E Value is an invalid /B value. Meaning: The minutes value for the SHUTDOWN command /b option was either non-numeric or exceeded 1440. SHUTDOWN was not executed. User Response: To use the /b option, enter a numeric value from 0 to 1440 immediately following the /b, as in /b75. LMU8004E /B option invalid -- LMUIPL.SYS not loaded by CONFIG.SYS. Meaning: The SHUTDOWN command with /b (re-IPL) option was issued for this machine, but the LMUIPL.SYS device driver is not installed. SHUTDOWN was not executed. User Response: To execute SHUTDOWN with the /b option, add the statement DEVICE=C:\LMU2\LMUIPL.SYS to CONFIG.SYS in this machine. LMU8006E Unable to execute LMUSDPM.EXE. Meaning: The SHUTDOWN command was issued for this machine, but SHUTDOWN could not locate the LMU/2 LMUSDPM command. User Response: Make sure that LMUSDPM.EXE is in a directory that is referenced by the PATH statement in CONFIG.SYS in this computer. LMU8007I Remote shutdown received from computername Meaning: The SHUTDOWN command was issued for this machine by the station identified by computername. This message appears in the log only. User Response: None. LMU8008I Remote shutdown cancelled. Meaning: The user at this machine cancelled a remotely-initiated SHUTDOWN, using the CANCEL button in the SHUTDOWN dialog. User Response: None. ΓòÉΓòÉΓòÉ 21.25. Numbered Messages (LMU9000 - LMU9999) ΓòÉΓòÉΓòÉ LMU9000E Invalid option opt Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked with option opt, which is not a valid option; processing is terminated. User Response: See the command format in topic LMUCMD, correct the command, and reissue LMUCMD. LMU9001E Invalid value specified for opt option Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked with an invalid value specified for option opt; processing is terminated. User Response: See the command format in topic LMUCMD, correct the command, and reissue LMUCMD. LMU9002E Required parameter {TARGET | COMMAND-STRING} not specified Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked without the indicated required parameter; processing is terminated. User Response: See the command format in topic LMUCMD, correct the command, and reissue LMUCMD. LMU9003E Invalid value specified for {TARGET | COMMAND-STRING} parameter Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked with a value for the indicated parameter that is: o Too long o Null o Not allowed with the other options specified. Processing is terminated. User Response: See the command format in topic LMUCMD, correct the command, and reissue LMUCMD. LMU9004W Profile error getting value for key keyname; rc = returncode Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for the key identified by keyname in the LMU.INI file; processing continues. There may be a problem in the LMU.INI file. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. If values were missing, correct the LMU/2 control file. 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU9005E Profile error getting value for required key keyname; rc = returncode Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for the required key identified by keyname in the LMU.INI file; processing is terminated. There may be a problem in the LMU.INI file. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. If values were missing, correct the LMU/2 control file. 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU9006E {DosLoadModule | DosGetProcAddr} failed for {module | function} name; rc = returncode Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code returncode from DosLoadModule or DosGetProcAddr for name while sending output to computer computer; processing is terminated. Possible causes for DosLoadModule include the following: o OS/2 LAN Requester or NetWare Requester for OS/2 is not installed o Missing LIBPATH specification in CONFIG.SYS. User Response: For DosLoadModule, install the required requester and/or update LIBPATH statement in CONFIG.SYS; reboot, then reissue LMUCMD. Otherwise, record the information in this message and contact IBM Software Support. LMU9010I Command sent to {managing system | target} computername[; waiting for output] Meaning: The LAN Management Utilities/2 Command software (LMUCMD) has sent the command string to computername successfully; processing is complete unless output is to be returned to the administrator workstation. User Response: If the wait is excessive or LMUCMD times out, check the following at the target workstation: 1. The LAN Management Utilities/2 Client software (LMUCLI) is executing in the target workstation. 2. LMURELAY.EXE and LMUCMDX.CMD are located in a directory that is referenced by the PATH statement in CONFIG.SYS at the target workstation. LMU9011E Error sending command to {managing system | target} computername; rc = returncode Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from the LAN Management Utilities/2 Send software (LMUSEND) while attempting to send the command string to computername; processing is terminated. User Response: Verify that the LAN Management Utilities/2 Server software (LMUSRV) or Client software (LMUCLI) is executing on computer computername. LMU9020I linenum: text Meaning: The LAN Management Utilities/2 Command software (LMUCMD) has received an output line from the target workstation. Linenum identifies the line number of the output record and text is the actual output text (which may be truncated); processing continues. User Response: None LMU9021I End-of-data Meaning: The LAN Management Utilities/2 Command software (LMUCMD) has finished relaying console output from the target station; processing completed successfully. User Response: None LMU9022W File I/O error Meaning: The LAN Management Utilities/2 Command software (LMUCMD) has detected an I/O error at the target station while relaying console output back to the administrator workstation; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9023W Console output from target is not supported Meaning: The LAN Management Utilities/2 Command software (LMUCMD) detected that the target workstation does not have support to relay console output back to the administrator workstation; processing is ended. User Response: None LMU9024I Output: Meaning: The LAN Management Utilities/2 Command software (LMUCMD) issues this message as a header for the console output text that follows; processing continues. User Response: None LMU9026E Time out occurred waiting for output Meaning: The LAN Management Utilities/2 Command software (LMUCMD) has timed out waiting for an output record from the target workstation; processing is terminated. User Response: Follow the actions in message LMU9010I. If the problem still exists, increase the time-out interval or use the default (wait forever). LMU9027E Invalid data (type xxxx) received Meaning: The LAN Management Utilities/2 Command software (LMUCMD) has received an output data record which is not one of the following: o A good-data record o An end-of-data record o An output-error record. Processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9030E {NCB.RESET | NCB.ADD.NAME | NCB.LISTEN | NCB.RECEIVE} for adapter adpnum failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from the indicated NETBIOS function using adapter adpnum; processing is terminated. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the NETBIOS return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU9031W NCB.HANG.UP for adapter adpnum failed; rc = X'returncode' Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from the NETBIOS NCB.HANG.UP function using adapter adpnum; processing continues. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the NETBIOS return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU9040E {SpxOpenSocket | SpxListenForConnection | SpxListenForConnectionPacket} failed; {rc | status} = X'code' Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code or status code from the indicated SPX function; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9041E DosSemWait for {SpxListenForConnection | SpxListenForConnectionPacket | SpxTerminateConnection} failed; rc = returncode Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from DosSemWait for the indicated SPX function; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9042W {SpxECBErrorCheck | SpxTerminateConnection | SpxCloseSocket} failed; {rc | status} = X'code' Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code or status code from the indicated SPX function; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU9043E Correlator mismatch detected Meaning: The LAN Management Utilities/2 Command software (LMUCMD) has detected a correlator mismatch; processing is terminated. User Response: Retry the command. LMU9050E {NetWkstaGetInfo | NetGetDCName | NetUserGetInfo} failed verifying administrator privilege level; rc = returncode Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from NetWkstaGetInfo, NetGetDCName, or NetUserGetInfo while verifying privilage level; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9051E OS/2 LAN Requester not started Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked on a workstation on which the OS/2 LAN Requester has not been started; processing is terminated. User Response: Start the OS/2 LAN Requester program, logon as an administrator, and reissue LMUCMD. LMU9052E Not logged on to server Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked on a workstation that is not logged on to the LAN; processing is terminated. User Response: Logon to the LAN as an administrator and reissue LMUCMD. LMU9053E Userid is not defined as an administrator to server dcname Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked on a workstation by a userid userid that is not defined in OS/2 User Profile Management (UPM) as an administrator to domain controller dcname; processing is terminated. User Response: Do one of the following: o Logon using a userid that is defined as an administrator o Change the UPM definition at dcname to specify userid as an administrator. Then, reissue LMUCMD. LMU9060E {NWGetDefaultConnectionID | NWGetConnectionNumber | NWGetConnectionInformation | NWGetBinderyAccessLevel} failed checking authorization; rc = X'returncode' Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from NWGetDefaultConnectionID, NWGetConnectionNumber, NWGetConnectionInformation, or NWGetBinderyAccessLevel while check authority; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9061E Not attached to server Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked on a workstation that is not attached to a NetWare server; processing is terminated. User Response: Attach to a NetWare server, login as a supervisor (or supervisor equivalent), and reissue LMUCMD. LMU9062E Not logged in to server Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked on a workstation that is not logged in to a NetWare server; processing is terminated. User Response: Login to a NetWare server as a supervisor (or supervisor equivalant) and reissue LMUCMD. LMU9063E Username is not defined as a supervisor equivalant to server nsname Meaning: The LAN Management Utilities/2 Command software (LMUCMD) was invoked on a workstation by a user username that is not defined as a supervisor or supervisor equivalant to NetWare server nsname; processing is terminated. User Response: Do one of the following: o Login using a user name that is defined as a supervisor or supervisor equivalent o Change the definition at nsname to specify username as a supervisor or supervisor equivalent. Then, reissue LMUCMD. LMU9070E NWGetConnectionList failed translating user name username; rc = X'returncode' Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from NWGetConnectionList while translating user name username; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9071E {NWGetConnectionID | NWGetObjectConnectionNumbers | NWGetInternetAddress} failed translating user name username on server nsname; rc = X'returncode' Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from the indicated function while translating user name username on NetWare server nsname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9072E Translation of user name username failed; not attached to server nsname Meaning: The LAN Management Utilities/2 Command software (LMUCMD) could not translate user name username because the workstation is not attached to the NetWare server nsname; processing is terminated. User Response: Attach to NetWare server nsname then reissue LMUCMD or use the internetwork address of username when invoking LMUCMD. LMU9073E User name username is not attached to server nsname Meaning: The LAN Management Utilities/2 Command software (LMUCMD) could not translate user name username because the user name username is not attached to the NetWare server nsname; processing is terminated. User Response: Use the internetwork address of username when invoking LMUCMD. LMU9074E User name username is attached to server nsname from multiple workstations Meaning: The LAN Management Utilities/2 Command software (LMUCMD) could not uniquely identify the internetwork address of user name username because username is attached to NetWare server nsname from multiple workstations; processing is terminated. This message is followed by other messages which provide the internetwork addresses of all workstations attached to nsname using username. User Response: Select the internetwork address of the correct workstation and reissue LMUCMD. LMU9075E User name username is not attached to any attached server Meaning: The LAN Management Utilities/2 Command software (LMUCMD) could not translate user name username because user name username not attached to any NetWare server this workstation is attached to; processing is terminated. User Response: Attach to the NetWare server that username is attached to then reissue LMUCMD or use the internetwork address of username when invoking LMUCMD. LMU9076E User name username is attached from multiple workstations Meaning: The LAN Management Utilities/2 Command software (LMUCMD) could not uniquely identify the internetwork address of user name username because username is attached from multiple workstations; processing is terminated. This message is followed by other messages which provide the internetwork addresses of all workstations attached using username. User Response: Select the internetwork address of the correct workstation and reissue LMUCMD. LMU9077W Internetwork address of workstation number is internetaddr Meaning: The LAN Management Utilities/2 Command software (LMUCMD) issues this message to provide the internetwork address internetaddr of workstation number; processing continues. User Response: None. LMU9078I Workstation number is attached to server nsname Meaning: The LAN Management Utilities/2 Command software (LMUCMD) issues this message to provide the name of the NetWare server nsname that workstation number is attached to; processing continues. User Response: None. LMU9079E Insufficient storage to translate user name username Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an error allocating storage while translating user name username; processing is terminated; User Response: Terminate applications that are not needed and reissue LMUCMD. LMU9080E {NWGetConnectionID | NWGetConnectionStatus} failed translating server nsname; rc = X'returncode' Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from NWGetConnectionID or NWGetConnectionStatus while translating NetWare server nsname; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9081E Translation of server nsname failed; not attached Meaning: The LAN Management Utilities/2 Command software (LMUCMD) could not translate NetWare server name nsname because the workstation is not attached to nsname; processing is terminated. User Response: Attach to NetWare server nsname then reissue LMUCMD or use the internetwork address of nsname when invoking LMUCMD. LMU9090E DosExitList failed {adding | removing} exit routine; rc = returncode Meaning: The LAN Management Utilities/2 Command software (LMUCMD) encountered an unexpected return code returncode from DosExitList; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9500E DosScanEnv for environment variable evar failed; rc = returncode Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code returncode from DosScanEnv; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9502E Error reading standard input Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected error reading standard input (STDIN); processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9503E Invalid option opt Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) was invoked with option opt, which is not a valid option; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9504E Invalid value specified for opt option Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) was invoked with an invalid value specified for option opt; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9505E Required parameter CORRELATOR not specified Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) was invoked without required parameter CORRELATOR; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9506E Invalid value specified for {CORRELATOR | SOCKET} parameter Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) was invoked with an invalid value specified for CORRELATOR or SOCKET parameters; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9507W Profile error getting value for key keyname; rc = returncode Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code returncode from the LAN Management Utilities/2 profile services routine (XQ4INI) attempting to get data for the key identified by keyname in the LMU.INI file; processing continues. There may be a problem in the LMU.INI file. User Response: Examine the messages prior to this one to determine if the LMU.INI file has been corrupted or is missing values. If so, 1. If values were missing, correct the LMU/2 control file. 2. Rebuild the LMU.INI by running the LINI.EXE program and specifying the LMU/2 control file as input. If rebuilding the LMU.INI file does not correct the problem, record the information in this message and contact IBM Software Support. LMU9508E DosExitList failed {adding | removing} exit routine while relaying output to computername; rc = returncode Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code returncode from DosExitList while sending output to computer computer; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9509E {DosLoadModule | DosGetProcAddr} failed for {module | function} name; rc = returncode Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code returncode from DosLoadModule or DosGetProcAddr for name while sending output to computer computer; processing is terminated. Possible causes for DosLoadModule include the following: o OS/2 LAN Requester or NetWare Requester for OS/2 is not installed o Missing LIBPATH specification in CONFIG.SYS. User Response: For DosLoadModule, install the required requester and/or update LIBPATH statement in CONFIG.SYS; reboot the workstation. Otherwise, record the information in this message and contact IBM Software Support. LMU9510E {SpxOpenSocket | IpxGetLocalTarget | SpxEstablishConnection | SpxSendSequencedPacket} failed while relaying output to computername; {rc | status} = X'code' Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code or status code from the indicated IPX or SPX function while sending output to computer computer; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9511E DosSemWait for {SpxEstablishConnection | SpxSendSequencedPacket | SpxTerminateConnection } failed while relaying output to computername; rc = returncode Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code returncode from DosSemWait for the indicated SPX function while sending output to computer computer; processing is terminated. User Response: Record the information in this message and contact IBM Software Support. LMU9512W {SpxECBErrorCheck | SpxTerminateConnection | SpxCloseSocket} failed while relaying output to computername; {rc | status} = X'code' Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code or status code from the indicated SPX function while sending output to computer computer; processing continues. User Response: Record the information in this message and contact IBM Software Support. LMU9520E {NCB.RESET | NCB.ADD.NAME | NCB.CALL | NCB.SEND} for adapter adpnum failed while relaying output to computername; rc = X'returncode' Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code returncode from the indicated NETBIOS function using adapter adpnum while sending output to computer computer; processing is terminated. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the NETBIOS return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU9521W NCB.HANG.UP for adapter adpnum failed while relaying output to computername; rc = X'returncode' Meaning: The LAN Management Utilities/2 Relay software (LMURELAY) encountered an unexpected return code returncode from the NETBIOS NCB.HANG.UP function using adapter adpnum while sending output to computer computer; processing continues. User Response: If you have a copy, refer to the IBM Local Area Network Technical Reference for the meaning of the NETBIOS return code and take action as appropriate. Otherwise, record the information in this message and contact IBM Software Support. LMU9999W DosGetMessage failed for message msgnum in file msgfile; rc = returncode Meaning: The LAN Management Utilities/2 Command software (LMUCMD) or Relay software (LMURELAY) encountered an unexpected return code returncode from DosGetMessage for message number msgnum; processing continues. User Response: When returncode is 2, verify that the message file msgfile is in the current directory or accessable via DPATH. Otherwise, record the information in this message and contact IBM Software Support. ΓòÉΓòÉΓòÉ 21.26. Numbered Messages (NSV0001 - NSV0030) ΓòÉΓòÉΓòÉ NSV0001E Unrecognized NSVWATCH start option option Meaning: The LAN Management Utilities/2 program NSVWATCH has been initiated with an invalid start option. User Response: Issue the NSVWATCH program with the help option (?) to determine the correct format of its options and reissue the command. NSV0002E GetServerInformation failed with rc hp1.returncode Meaning: The LAN Management Utilities/2 program NSVWATCH has encountered an error while attempting to obtain server information. User Response: Record the message information and contact IBM Software Support. NSV0003E Error sending information to LMU/2 database, rc = returncode Meaning: The LAN Management Utilities/2 program NSVWATCH has received an error trying to send the collected server information to the LMU/2 database machine. User Response: Run the LMULOAD program to ensure that the LMU/2 database machine has been specified correctly. If not, correct the database machine value and reissue the NSVWATCH command. If the database machine has been specified correctly, record the information in this message and contact IBM Software Support. NSV0004I Transport of data to LMU/2 database machine completed, rc = returncode Meaning: The LAN Management Utilities/2 program NSVWATCH has attempted to send server data to the LMU/2 database machine. User Response: If returncode is zero, no error has occured. If not, check the previous messages in the LMU/2 message log to determine the cause of the error. NSV0005E Invalid NSVWATCH start option option Meaning: The LAN Management Utilities/2 program NSVWATCH has been initiated with an invalid start option. User Response: Issue the NSVWATCH program with the help option (?) to determine the correct format of its options and reissue the command. NSV0006I Server utilization at current percentage threshold percentage Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the average CPU utilization over the polling interval is at current percentage. This is more than the threshhold precentage threshold percentage. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0007I File Opens at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of file opens over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0008I File Creates at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of file creates over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0009I File Renames at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of file renames over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0010I File Deletes at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of file deletes over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0011I Directory Searches at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of directory searches over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0012I File Reads at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of file reads over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0013I File Writes at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of file writes over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0014I File Bytes Read at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of file bytes read (in k) over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0015I File Bytes Written at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of file bytes written (in k) over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0016I FAT Sectors Dirty at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of FAT sectors dirty over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0017I FAT Sectors Written at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of FAT sectors written over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0018I Packets Received at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of packets received over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. NSV0019I Packets Transmitted at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of packets transmitted over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0020I Bytes Received at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of bytes received (in k) over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0021I Bytes Transmitted at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of bytes transmitted (in k) over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0022I Packets Routed at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of packets routed over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0023I Record Locks at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of record locks over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0024I Transactions at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the number of transactions over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0025I Average connections at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the average number of connections over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0026I Peak connections at current number threshold number Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the peak number of connections over the polling interval is at current number. This is more than the threshhold number threshold number. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. NSV0027I Peak utilization at current percentage threshold percentage Meaning: The LAN Management Utilities/2 program NSVWATCH has discovered that the peak CPU utilizatino over the polling interval is at current percentage. This is more than the threshhold percentage threshold percentage. An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. ΓòÉΓòÉΓòÉ 21.27. Numbered Messages (VOL0001 - VOL0010) ΓòÉΓòÉΓòÉ VOL0001E Unrecognized VOLWATCH start option option Meaning: The LAN Management Utilities/2 program VOLWATCH has been initiated with an invalid start option. User Response: Issue the VOLWATCH program with the help option (?) to determine the correct format of its options and reissue the command. VOL0002E GetvolumeInformation for volume volumename returned with rc returncode Meaning: The LAN Management Utilities/2 program VOLWATCH has received an error trying to obtain information about volume volumename User Response: Record the information in this message and contact IBM Software Support. VOL0003E Error sending information to LMU/2 database, rc = returncode Meaning: The LAN Management Utilities/2 program VOLWATCH has received an error trying to send the collected volume information to the LMU/2 database machine. User Response: Run the LMULOAD program to ensure that the LMU/2 database machine has been specified correctly. If not, correct the database machine value and reissue the VOLWATCH command. If the database machine has been specified correctly, record the information in this message and contact IBM Software Support. VOL0004I Transport of data to LMU/2 database machine completed, rc = returncode Meaning: The LAN Management Utilities/2 program VOLWATCH has attempted to send volume data to the LMU/2 database machine. User Response: If returncode is zero, no error has occured. If not, check the previous messages in the LMU/2 message log to determine the cause of the error. VOL0005E Invalid VOLWATCH start option option Meaning: The LAN Management Utilities/2 program VOLWATCH has been initiated with an invalid start option. User Response: Issue the VOLWATCH program with the help option (?) to determine the correct format of its options and reissue the command. VOL0006I Volume volumename AVB at current percentage threshold percentage Meaning: The LAN Management Utilities/2 client program VOLWATCH has discovered that the available block space for volume volumename is at current percentage. This is less than the threshhold precentage threshold percentage that VOLWATCH An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. VOL0007I Volume volumename ADS at current percentage threshold percentage Meaning: The LAN Management Utilities/2 client program VOLWATCH has discovered that the available directory slot space for volume volumename is at current percentage. This is less than the threshhold precentage threshold percentage that VOLWATCH An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. VOL0008I Volume volumename PGB at current percentage threshold percentage Meaning: The LAN Management Utilities/2 client program VOLWATCH has discovered that the purgeable block space for volume volumename is at current percentage. This is more than the threshhold precentage threshold percentage that VOLWATCH An alert has been generated and sent to the LMU/2 Fault manager. User Response: Notify your system administrator of the condition. VOL0009I Volume volumename Dismounted Meaning: The LAN Management Utilities/2 client program VOLWATCH has discovered that volumename has been dismounted. User Response: Notify your system administrator of the condition. VOL0010E Unable to set screen autodestruction mode Meaning: The LAN Management Utilities/2 client program VOLWATCH has encountered an error attempting to cause its NLM screen to close automatically. User Response: Record the message information and contact IBM Software Support. ΓòÉΓòÉΓòÉ 22. LAN Management Utilities/2 Database Tables ΓòÉΓòÉΓòÉ The LAN Management Utilities/2 database is an IBM OS/2 Database Manager database in a managing system. It contains vital product data (configuration data) collected by the QUERYVPD and QDOSVPD utilities, and performance data collected by the PERFCAP utility (OS/2) or by the NSVWATCH or VOLWATCH utilities (NetWare Server). See o Vital Product Data for the configuration data views and tables o Performance Data for the performance data tables o Data Cross Reference for a cross-reference of all data items in the tables. To upload the tables to a host, modify the DBMTODB2.SMP sample REXX procedure to create a DBMTODB2.CMD file that suits your installation. Use the DBMTODB2.CMD utility to convert and transmit the LMU/2 DBM database tables to an MVS host system. The database tables can then be imported into the host IBM Database 2 (DB2) database. This provides central data management at the host. ΓòÉΓòÉΓòÉ 22.1. Vital Product Data Tables ΓòÉΓòÉΓòÉ As a result of executing QUERYVPD and QDOSVPD, configuration data tables are created or appended in the LMU/2 database. The tables and their column names, along with a description, are listed in the following topics: o Adapter Table o Base Table o Component Table o Diskette Table o Display Table o Drive Table o File Table o Fixed_Disk Table o Expansion_Slot Table o Keyboard Table o Model Table o Serial Port Table o Syslevel Table o User Data Table Views supplied with LMU/2 are described in Vital Product Data Views. ΓòÉΓòÉΓòÉ 22.1.1. Adapter Table ΓòÉΓòÉΓòÉ The adapter table provides the translation from ADAPTER_ID (in expansion_slot table) to adapter name. CREATE TABLE adapter (ADAPTER_ID CHAR(4) NOT NULL, ADAPTER_NAME VARCHAR(70) , PRIMARY KEY (ADAPTER_ID)); ΓòÉΓòÉΓòÉ 22.1.2. Base Table ΓòÉΓòÉΓòÉ The base table contains base configuration information. CREATE TABLE base (COMPUTER VARCHAR(21) NOT NULL, REPORT_DATE DATE NOT NULL, REPORT_TIME TIME NOT NULL, NODE_TYPE CHAR(4) , DOMAIN VARCHAR(15) , USERID VARCHAR(48) , MANAGING_SYSTEM VARCHAR(48) , OPERATING_SYSTEM VARCHAR(80) NOT NULL, VERSION VARCHAR(12) NOT NULL, MODEL CHAR(11) NOT NULL, PRODUCT_NUMBER VARCHAR(8) , VIDEO VARCHAR(4) , VIDEO_MEMORY INTEGER , DISPLAY SMALLINT NOT NULL, KEYBOARD_ID CHAR(4) NOT NULL, PLANAR_ID CHAR(4) , COPROCESSOR VARCHAR(7) , DISKETTE_DRIVES SMALLINT NOT NULL, FIXED_DISKS SMALLINT NOT NULL, PARALLEL_PORTS SMALLINT NOT NULL, SERIAL_PORTS SMALLINT NOT NULL, TOTAL_MEMORY INTEGER NOT NULL, BIOS DATE , NODE_ADDRESS CHAR(12) , UNIVERSAL_ADDRESS CHAR(12) , PRIMARY KEY (COMPUTER)); ΓòÉΓòÉΓòÉ 22.1.3. Component Table ΓòÉΓòÉΓòÉ The component table provides the translation from FILE_EXTENSION (syslevel table) to program name. CREATE TABLE component (FILE_EXTENSION VARCHAR(3) NOT NULL, PROGRAM_NAME VARCHAR(80) , PRIMARY KEY (FILE_EXTENSION)); ΓòÉΓòÉΓòÉ 22.1.4. Diskette Table ΓòÉΓòÉΓòÉ The diskette table contains diskette configuration information. CREATE TABLE diskette (COMPUTER VARCHAR(21) NOT NULL, DISKETTE SMALLINT NOT NULL, TYPE SMALLINT NOT NULL, CAPACITY INTEGER , TRACKS SMALLINT , FORMAT VARCHAR(5) , FOREIGN KEY COMPUTER (COMPUTER) REFERENCES BASE ON DELETE CASCADE); ΓòÉΓòÉΓòÉ 22.1.5. Display Table ΓòÉΓòÉΓòÉ The display table provides the translation from DISPLAY (base table) to display name. CREATE TABLE display (DISPLAY SMALLINT NOT NULL, DISPLAY_NAME VARCHAR(25) , PRIMARY KEY (DISPLAY)); ΓòÉΓòÉΓòÉ 22.1.6. Drive Table ΓòÉΓòÉΓòÉ The drive table contains logical drive configuration information. CREATE TABLE drive (COMPUTER VARCHAR(21) NOT NULL, DRIVE CHAR(1) NOT NULL, TYPE VARCHAR(8) NOT NULL, SIZE INTEGER NOT NULL, AVAILABLE INTEGER NOT NULL, VOLUME_NUMBER SMALLINT , VOLUME VARCHAR(16) , NETWORK_NAME VARCHAR(260) , CURRENT_DIRECTORY VARCHAR(260) , FOREIGN KEY COMPUTER (COMPUTER) REFERENCES BASE ON DELETE CASCADE); ΓòÉΓòÉΓòÉ 22.1.7. File Table ΓòÉΓòÉΓòÉ CREATE TABLE file (COMPUTER VARCHAR(21) NOT NULL, NAME VARCHAR(260) NOT NULL, LOCATION VARCHAR(260) , LAST_WRITTEN TIMESTAMP , SIZE INTEGER , FOREIGN KEY COMPUTER (COMPUTER) REFERENCES BASE ON DELETE CASCADE); ΓòÉΓòÉΓòÉ 22.1.8. Fixed_Disk Table ΓòÉΓòÉΓòÉ The fixed_disk table contains fixed disk configuration information. CREATE TABLE fixed_disk (COMPUTER VARCHAR(21) NOT NULL, DISK SMALLINT NOT NULL, SIZE INTEGER NOT NULL, CYLINDERS INTEGER NOT NULL, SECTORS_PER_CYL INTEGER NOT NULL, HEADS INTEGER NOT NULL, TOTAL_SECTORS INTEGER NOT NULL, FOREIGN KEY COMPUTER (COMPUTER) REFERENCES BASE ON DELETE CASCADE); ΓòÉΓòÉΓòÉ 22.1.9. Expansion_Slot Table ΓòÉΓòÉΓòÉ The expansion_slot table contains expansion slot configuration information. CREATE TABLE expansion_slot (COMPUTER VARCHAR(21) NOT NULL, SLOT SMALLINT NOT NULL, ADAPTER_ID CHAR(4) NOT NULL, STATUS VARCHAR(8) NOT NULL, POS_DATA CHAR(8) NOT NULL, SUB_ADDRESS CHAR(4) NOT NULL, INTERRUPT_LEVEL SMALLINT , IO_ADDRESS CHAR(9) , RAM_ADDRESS_RANGE CHAR(11) , ROM_ADDRESS_RANGE CHAR(11) , ADAPTER CHAR(3) , ADAPTER_SPEED SMALLINT , NODE_ADDRESS CHAR(12) , UNIVERSAL_ADDRESS CHAR(12) , SUPPLEMENTAL_1 VARCHAR(80) , SUPPLEMENTAL_2 VARCHAR(80) , SUPPLEMENTAL_3 VARCHAR(80) , SUPPLEMENTAL_4 VARCHAR(80) , SUPPLEMENTAL_5 VARCHAR(80) , SUPPLEMENTAL_6 VARCHAR(80) , SUPPLEMENTAL_7 VARCHAR(80) , SUPPLEMENTAL_8 VARCHAR(80) , SUPPLEMENTAL_9 VARCHAR(80) , SUPPLEMENTAL_10 VARCHAR(80) , SUPPLEMENTAL_11 VARCHAR(80) , SUPPLEMENTAL_12 VARCHAR(80) , FOREIGN KEY COMPUTER (COMPUTER) REFERENCES BASE ON DELETE CASCADE); ΓòÉΓòÉΓòÉ 22.1.10. Keyboard Table ΓòÉΓòÉΓòÉ The keyboard table provides the translation from KEYBOARD_ID (base table) to keyboard name. CREATE TABLE keyboard (KEYBOARD_ID CHAR(4) NOT NULL, KEYBOARD_NAME VARCHAR(30) , PRIMARY KEY (KEYBOARD_ID)); ΓòÉΓòÉΓòÉ 22.1.11. Model Table ΓòÉΓòÉΓòÉ The model table provides the translation from MODEL (Base table) to model-dependent information (for example, processor and processor speed). CREATE TABLE model (MODEL CHAR(11) NOT NULL, MACHINE_NAME VARCHAR(30) , PROCESSOR VARCHAR(7) , PROCESSOR_SPEED SMALLINT , BUS VARCHAR(20) , EXPANSION_SLOTS SMALLINT , USER_SLOTS SMALLINT , PRIMARY KEY (MODEL)); ΓòÉΓòÉΓòÉ 22.1.12. Serial Port Table ΓòÉΓòÉΓòÉ The serial port table contains configuration information for serial ports. CREATE TABLE serial_port (COMPUTER VARCHAR(21) NOT NULL, PORT SMALLINT NOT NULL, NAME VARCHAR(6) NOT NULL, BAUD_RATE INTEGER NOT NULL, DATA_BITS SMALLINT , PARITY VARCHAR(5) , STOP_BITS VARCHAR(4) , FOREIGN KEY COMPUTER (COMPUTER) REFERENCES BASE ON DELETE CASCADE); ΓòÉΓòÉΓòÉ 22.1.13. Syslevel Table ΓòÉΓòÉΓòÉ The syslevel table contains CSD configuration information for installed software. CREATE TABLE syslevel (COMPUTER VARCHAR(21) NOT NULL, FILE_EXTENSION VARCHAR(3) NOT NULL, DRIVE CHAR(1) NOT NULL, PATH VARCHAR(260) , COMPONENT_ID VARCHAR(9) NOT NULL, VERSION VARCHAR(12) NOT NULL, CURRENT_CSD VARCHAR(7) NOT NULL, PREVIOUS_CSD VARCHAR(7) NOT NULL, FOREIGN KEY COMPUTER (COMPUTER) REFERENCES BASE ON DELETE CASCADE); ΓòÉΓòÉΓòÉ 22.1.14. User Data Table ΓòÉΓòÉΓòÉ The user data table contains data defined by the user in a USERVPD.DAT file in the workstation. CREATE TABLE user_data (COMPUTER VARCHAR(21) NOT NULL, USER_DATA VARCHAR(3500) , FOREIGN KEY COMPUTER (COMPUTER) REFERENCES BASE ON DELETE CASCADE); ΓòÉΓòÉΓòÉ 22.2. Vital Product Data Views ΓòÉΓòÉΓòÉ The predefined views supplied with LMU/2 are: o Config o Configuration o Hardware o Software ΓòÉΓòÉΓòÉ 22.2.1. Config View ΓòÉΓòÉΓòÉ The config view combines the base table and user data table. CREATE VIEW config (COMPUTER, REPORT_DATE, REPORT_TIME, NODE_TYPE, DOMAIN, USERID, MANAGING_SYSTEM, OPERATING_SYSTEM, VERSION, MODEL, PRODUCT_NUMBER, VIDEO, VIDEO_MEMORY, DISPLAY, KEYBOARD_ID, PLANAR_ID, COPROCESSOR, DISKETTE_DRIVES, FIXED_DISKS, PARALLEL_PORTS, SERIAL_PORTS, TOTAL_MEMORY, BIOS, NODE_ADDRESS, UNIVERSAL_ADDRESS, USER_DATA) AS SELECT A.COMPUTER, REPORT_DATE, REPORT_TIME, NODE_TYPE, DOMAIN, USERID, MANAGING_SYSTEM, OPERATING_SYSTEM, VERSION, MODEL, PRODUCT_NUMBER, VIDEO, VIDEO_MEMORY, DISPLAY, KEYBOARD_ID, PLANAR_ID, COPROCESSOR, DISKETTE_DRIVES, FIXED_DISKS, PARALLEL_PORTS, SERIAL_PORTS, TOTAL_MEMORY, BIOS, NODE_ADDRESS, UNIVERSAL_ADDRESS, USER_DATA FROM BASE A, USER_DATA B WHERE (A.COMPUTER = B.COMPUTER); ΓòÉΓòÉΓòÉ 22.2.2. Configuration View ΓòÉΓòÉΓòÉ The configuration view combines the base, display, keyboard, and model tables. CREATE VIEW configuration (COMPUTER, REPORT_DATE, REPORT_TIME, NODE_TYPE, DOMAIN, USERID, MANAGING_SYSTEM, OPERATING_SYSTEM, VERSION, MODEL, MACHINE_NAME, PRODUCT_NUMBER, VIDEO, VIDEO_MEMORY, DISPLAY, DISPLAY_NAME, KEYBOARD_ID, KEYBOARD_NAME, PLANAR_ID, PROCESSOR, PROCESSOR_SPEED, COPROCESSOR, BUS, DISKETTE_DRIVES, FIXED_DISKS, PARALLEL_PORTS, SERIAL_PORTS, EXPANSION_SLOTS, USER_SLOTS, TOTAL_MEMORY, BIOS, NODE_ADDRESS, UNIVERSAL_ADDRESS) AS SELECT A.COMPUTER, REPORT_DATE, REPORT_TIME, NODE_TYPE, DOMAIN, USERID, MANAGING_SYSTEM, OPERATING_SYSTEM, VERSION, A.MODEL, MACHINE_NAME, PRODUCT_NUMBER, VIDEO, VIDEO_MEMORY, A.DISPLAY, DISPLAY_NAME, A.KEYBOARD_ID, KEYBOARD_NAME, PLANAR_ID, PROCESSOR, PROCESSOR_SPEED, COPROCESSOR, BUS, DISKETTE_DRIVES, FIXED_DISKS, PARALLEL_PORTS, SERIAL_PORTS, EXPANSION_SLOTS, USER_SLOTS, TOTAL_MEMORY, BIOS, NODE_ADDRESS, UNIVERSAL_ADDRESS FROM BASE A, DISPLAY B, KEYBOARD C, MODEL D WHERE (A.DISPLAY = B.DISPLAY AND A.KEYBOARD_ID = C.KEYBOARD_ID AND A.MODEL = D.MODEL); ΓòÉΓòÉΓòÉ 22.2.3. Hardware View ΓòÉΓòÉΓòÉ The hardware view combines the adapter and expansion_slot tables. CREATE VIEW hardware (COMPUTER, SLOT, ADAPTER_ID, ADAPTER_NAME, STATUS, POS_DATA, SUB_ADDRESS, INTERRUPT_LEVEL, IO_ADDRESS, RAM_ADDRESS_RANGE, ROM_ADDRESS_RANGE, ADAPTER, ADAPTER_SPEED, NODE_ADDRESS, UNIVERSAL_ADDRESS, SUPPLEMENTAL_1, SUPPLEMENTAL_2, SUPPLEMENTAL_3, SUPPLEMENTAL_4, SUPPLEMENTAL_5, SUPPLEMENTAL_6, SUPPLEMENTAL_7, SUPPLEMENTAL_8, SUPPLEMENTAL_9, SUPPLEMENTAL_10, SUPPLEMENTAL_11, SUPPLEMENTAL_12) AS SELECT COMPUTER, SLOT, A.ADAPTER_ID, ADAPTER_NAME, STATUS, POS_DATA, SUB_ADDRESS, INTERRUPT_LEVEL, IO_ADDRESS, RAM_ADDRESS_RANGE, ROM_ADDRESS_RANGE, ADAPTER, ADAPTER_SPEED, NODE_ADDRESS, UNIVERSAL_ADDRESS, SUPPLEMENTAL_1, SUPPLEMENTAL_2, SUPPLEMENTAL_3, SUPPLEMENTAL_4, SUPPLEMENTAL_5, SUPPLEMENTAL_6, SUPPLEMENTAL_7, SUPPLEMENTAL_8, SUPPLEMENTAL_9, SUPPLEMENTAL_10, SUPPLEMENTAL_11, SUPPLEMENTAL_12 FROM EXPANSION_SLOT A, ADAPTER B WHERE (A.ADAPTER_ID = B.ADAPTER_ID); ΓòÉΓòÉΓòÉ 22.2.4. Software View ΓòÉΓòÉΓòÉ The software view combines the component and syslevel tables. CREATE VIEW software (COMPUTER, FILE_EXTENSION, DRIVE, PATH, COMPONENT_ID, PROGRAM_NAME, VERSION, CURRENT_CSD, PREVIOUS_CSD) AS SELECT COMPUTER, A.FILE_EXTENSION, DRIVE, PATH, COMPONENT_ID, PROGRAM_NAME, VERSION, CURRENT_CSD, PREVIOUS_CSD FROM SYSLEVEL A, COMPONENT B WHERE (A.FILE_EXTENSION = B.FILE_EXTENSION); ΓòÉΓòÉΓòÉ 22.3. Performance Data Tables (OS/2 Requesters) ΓòÉΓòÉΓòÉ As a result of executing PERFCAP, several tables of performance data from OS/2 LAN Requesters are created or appended at the database machine. o Process Table. o Disk Table. o Swap Table. o Memory Table. o Logical Disk Table. A cross-reference of all data in the tables is found in Data Cross Reference. ΓòÉΓòÉΓòÉ 22.3.1. Process Table ΓòÉΓòÉΓòÉ The Process table provides SPM/2 data on processes in the workstation. CREATE TABLE process (COMPUTER VARCHAR(21) NOT NULL, REPORT_DATE DATE NOT NULL, REPORT_TIME TIME NOT NULL, TIME_INTERVAL INTEGER NOT NULL, ACTUAL_INTERVAL FLOAT NOT NULL, PROCESS_ID CHAR(4) NOT NULL, PROCESS_NAME VARCHAR(8) NOT NULL, DISPATCHES INTEGER NOT NULL, EXECUTION_TIME FLOAT NOT NULL, INTERRUPT_TIME FLOAT NOT NULL); ΓòÉΓòÉΓòÉ 22.3.2. Disk Table ΓòÉΓòÉΓòÉ The Disk table provides SPM/2 data on physical disk activity in the workstation. CREATE TABLE disk (COMPUTER VARCHAR(21) NOT NULL, REPORT_DATE DATE NOT NULL, REPORT_TIME TIME NOT NULL, TIME_INTERVAL INTEGER NOT NULL, ACTUAL_INTERVAL FLOAT NOT NULL, DISK_ID CHAR(4) NOT NULL, READS INTEGER NOT NULL, SECTORS_READ INTEGER NOT NULL, READ_TIME FLOAT NOT NULL, WRITES INTEGER NOT NULL, SECTORS_WRITTEN INTEGER NOT NULL, WRITE_TIME FLOAT NOT NULL, VERIFIES INTEGER NOT NULL, SECTORS_VERIFIED INTEGER NOT NULL, VERIFY_TIME FLOAT NOT NULL); ΓòÉΓòÉΓòÉ 22.3.3. Swap Table ΓòÉΓòÉΓòÉ The Swap table provides SPM/2 data on swap activity in the workstation. CREATE TABLE swap (COMPUTER VARCHAR(21) NOT NULL, REPORT_DATE DATE NOT NULL, REPORT_TIME TIME NOT NULL, TIME_INTERVAL INTEGER NOT NULL, ACTUAL_INTERVAL FLOAT NOT NULL, SWAP_IN_COUNT INTEGER NOT NULL, BYTES_SWAPPED_IN INTEGER NOT NULL, SWAP_IN_TIME FLOAT NOT NULL, SWAP_OUT_COUNT INTEGER NOT NULL, BYTES_SWAPPED_OUT INTEGER NOT NULL, SWAP_OUT_TIME FLOAT NOT NULL); ΓòÉΓòÉΓòÉ 22.3.4. Memory Table ΓòÉΓòÉΓòÉ The Memory table provides SPM/2 data on RAM Memory utilization in the workstation. CREATE TABLE memory (COMPUTER VARCHAR(21) NOT NULL, REPORT_DATE DATE NOT NULL, REPORT_TIME TIME NOT NULL, TIME_INTERVAL INTEGER NOT NULL, ACTUAL_INTERVAL FLOAT , TOTAL_INSTALLED INTEGER NOT NULL, AVAILABLE INTEGER NOT NULL, WORKING_SET INTEGER NOT NULL, NOT_WORKING_SET INTEGER NOT NULL, FREE INTEGER NOT NULL); ΓòÉΓòÉΓòÉ 22.3.5. Logical Disk Table ΓòÉΓòÉΓòÉ The Logical Disk table provides SPM/2 data on DOS Open/Close/Read/Write in the workstation. CREATE TABLE logical_disk (COMPUTER VARCHAR(21) NOT NULL, REPORT_DATE DATE NOT NULL, REPORT_TIME TIME NOT NULL, TIME_INTERVAL INTEGER NOT NULL, ACTUAL_INTERVAL FLOAT , FILE_HANDLE CHAR(4) NOT NULL, FILE_NAME VARCHAR(260) , PROCESS_ID CHAR(4) NOT NULL, PROCESS_NAME VARCHAR(8) NOT NULL, LAST_ACTION VARCHAR(4) NOT NULL, BYTES_READ INTEGER NOT NULL, BYTES_WRITTEN INTEGER NOT NULL); ΓòÉΓòÉΓòÉ 22.4. Performance Data Tables (NetWare Servers) ΓòÉΓòÉΓòÉ As a result of executing the NSVWATCH or VOLWATCH utilities several tables of performance data for NetWare Servers are created or appended at the database machine. o Server Table. o Volume Table. ΓòÉΓòÉΓòÉ 22.4.1. Server Table ΓòÉΓòÉΓòÉ The Server table provides performance statistics about the NetWare Server. CREATE TABLE server (COMPUTER VARCHAR(21) NOT NULL, REPORT_DATE DATE NOT NULL, REPORT_TIME TIME NOT NULL, UTILIZATION INTEGER NOT NULL, PEAK_UTILIZATION INTEGER NOT NULL, FILE_OPENS INTEGER NOT NULL, WRAP_FILE_OPENS INTEGER NOT NULL, FILE_CREATES INTEGER NOT NULL, WRAP_FILE_CREATES INTEGER NOT NULL, FILE_RENAMES INTEGER NOT NULL, WRAP_FILE_RENAMES INTEGER NOT NULL, FILE_DELETES INTEGER NOT NULL, WRAP_FILE_DELETES INTEGER NOT NULL, DIRECTORY_SEARCHES INTEGER NOT NULL, WRAP_DIR_SEARCHES INTEGER NOT NULL, FILE_READS INTEGER NOT NULL, WRAP_FILE_READS INTEGER NOT NULL, FILE_WRITES INTEGER NOT NULL, WRAP_FILE_WRITES INTEGER NOT NULL, FILE_BYTES_READ INTEGER NOT NULL, WRAP_FBYTE_READ INTEGER NOT NULL, FILE_BYTES_WRITTEN INTEGER NOT NULL, WRAP_FBYTE_WRITTEN INTEGER NOT NULL, DISK_READS INTEGER NOT NULL, WRAP_DISK_READS INTEGER NOT NULL, DISK_WRITES INTEGER NOT NULL, WRAP_DISK_WRITES INTEGER NOT NULL, DISK_BYTES_READ INTEGER NOT NULL, WRAP_DBYTE_READ INTEGER NOT NULL, DISK_BYTES_WRITTEN INTEGER NOT NULL, WRAP_DBYTE_WRITTEN INTEGER NOT NULL, FAT_SECTS_DIRTY INTEGER NOT NULL, WRAP_SECTS_DIRTY INTEGER NOT NULL, FAT_SECTS_WRITTEN INTEGER NOT NULL, WRAP_SECTS_WRITTEN INTEGER NOT NULL, PKTS_RECEIVED INTEGER NOT NULL, WRAP_PKTS_RECEIVED INTEGER NOT NULL, PKTS_TRANSMITTED INTEGER NOT NULL, WRAP_PKTS_XMITTED INTEGER NOT NULL, BYTES_RECEIVED INTEGER NOT NULL, WRAP_BYTES_RECVD INTEGER NOT NULL, BYTES_TRANSMITTED INTEGER NOT NULL, WRAP_BYTES_XMITTED INTEGER NOT NULL, PKTS_ROUTED INTEGER NOT NULL, WRAP_PKTS_ROUTED INTEGER NOT NULL, REQUESTS INTEGER NOT NULL, WRAP_REQUESTS INTEGER NOT NULL, RECORD_LOCKS INTEGER NOT NULL, WRAP_RECORD_LOCKS INTEGER NOT NULL, TRANSACTIONS INTEGER NOT NULL, WRAP_TRANSACTIONS INTEGER NOT NULL, CONNECTIONS INTEGER NOT NULL, PEAK_CONNECTIONS INTEGER NOT NULL); ΓòÉΓòÉΓòÉ 22.4.2. Volume Table ΓòÉΓòÉΓòÉ The Volume table provides performance statistics about disk volumes on a NetWare Server. CREATE TABLE volume (COMPUTER VARCHAR(21) NOT NULL, REPORT_DATE DATE NOT NULL, REPORT_TIME TIME NOT NULL, VOLUME_NAME VARCHAR(16) NOT NULL, VOLUME_NUMBER SMALLINT NOT NULL, DRIVE_NUMBER SMALLINT NOT NULL, ELAPSED_TIME INTEGER NOT NULL, SECTORS_PER_BLOCK INTEGER NOT NULL, STARTING_BLOCK INTEGER NOT NULL, TOTAL_BLOCKS INTEGER NOT NULL, AVAILABLE_BLOCKS INTEGER NOT NULL, TOTAL_DIR_SLOTS INTEGER NOT NULL, AVAIL_DIR_SLOTS INTEGER NOT NULL, MAX_DIR_SLOTS_USED INTEGER NOT NULL, HASHING CHAR(1) NOT NULL, REMOVABLE CHAR(1) NOT NULL, MOUNTED CHAR(1) NOT NULL, PURGEABLE_BLOCKS INTEGER NOT NULL); ΓòÉΓòÉΓòÉ 22.5. Data Cross-Reference ΓòÉΓòÉΓòÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé COLUMN NAME Γöé SQL TYPE Γöé TABLE NAME Γöé DESCRIPTION Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Actual_Interval Γöé FLOAT Γöé Disk Γöé Actual time interval of Γöé Γöé Γöé Γöé Logical_Disk Γöé performance collection Γöé Γöé Γöé Γöé Memory Γöé interval (in seconds) Γöé Γöé Γöé Γöé Process Γöé Γöé Γöé Γöé Γöé Swap Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Adapter Γöé CHAR(3) Γöé Expansion_Slot Γöé Token-Ring Network Γöé Γöé Γöé Γöé Γöé adapter role (PRI or ALT) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Adapter_Id Γöé CHAR(4) Γöé Adapter Γöé Adapter card identifier Γöé Γöé Γöé Γöé Expansion_Slot Γöé (in hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Adapter_Speed Γöé SMALLINT Γöé Expansion_Slot Γöé Token-Ring Network Γöé Γöé Γöé Γöé Γöé adapter speed (in mega- Γöé Γöé Γöé Γöé Γöé bytes) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Adapter_Name Γöé VARCHAR(70) Γöé Adapter Γöé Adapter name Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Available Γöé INTEGER Γöé Drive Γöé Available space on Γöé Γöé Γöé Γöé Memory Γöé logical drive (in kilo- Γöé Γöé Γöé Γöé Γöé bytes) Γöé Γöé Γöé Γöé Γöé Available memory Γöé Γöé Γöé Γöé Γöé (swappable, not fixed; in Γöé Γöé Γöé Γöé Γöé bytes) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Available_Blocks Γöé INTEGER Γöé Volume Γöé Number of avaliable blocksΓöé Γöé Γöé Γöé Γöé on this volume Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Avail_Dir_Slots Γöé INTEGER Γöé Volume Γöé Total number of available Γöé Γöé Γöé Γöé Γöé directory slots for this Γöé Γöé Γöé Γöé Γöé volume Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Baud_Rate Γöé INTEGER Γöé Serial_Port Γöé Baud rate Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé BIOS Γöé DATE Γöé Base Γöé Basic I/O Services (BIOS) Γöé Γöé Γöé Γöé Γöé level Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Bus Γöé VARCHAR(20) Γöé Model Γöé Bus Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Bytes_Read Γöé INTEGER Γöé Logical_Disk Γöé Total number of bytes Γöé Γöé Γöé Γöé Γöé read during the col- Γöé Γöé Γöé Γöé Γöé lection interval Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Bytes_Received Γöé INTEGER Γöé Server Γöé Number of bytes received Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Bytes_Swapped_In Γöé INTEGER Γöé Swap Γöé Total number of bytes Γöé Γöé Γöé Γöé Γöé swapped in Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Bytes_Swapped_Out Γöé INTEGER Γöé Swap Γöé Total number of bytes Γöé Γöé Γöé Γöé Γöé swapped out Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Bytes_Transmitted Γöé INTEGER Γöé Server Γöé Number of bytes Γöé Γöé Γöé Γöé Γöé transmitted since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Bytes_Written Γöé INTEGER Γöé Logical_Disk Γöé Total number of bytes Γöé Γöé Γöé Γöé Γöé written during the col- Γöé Γöé Γöé Γöé Γöé lection interval Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Capacity Γöé INTEGER Γöé Diskette Γöé Diskette capacity (in Γöé Γöé Γöé Γöé Γöé kilobytes) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Component_Id Γöé VARCHAR(9) Γöé SysLevel Γöé Component identifier Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Computer Γöé VARCHAR(21) Γöé Base Γöé IBM LAN Requester com- Γöé Γöé Γöé Γöé Disk Γöé puter name or Novell Γöé Γöé Γöé Γöé Diskette Γöé NetWare node address Γöé Γöé Γöé Γöé Drive Γöé Γöé Γöé Γöé Γöé Expansion_Slot Γöé Γöé Γöé Γöé Γöé File Γöé Γöé Γöé Γöé Γöé Fixed_Disk Γöé Γöé Γöé Γöé Γöé Logical_Disk Γöé Γöé Γöé Γöé Γöé Memory Γöé Γöé Γöé Γöé Γöé Process Γöé Γöé Γöé Γöé Γöé Server Γöé Γöé Γöé Γöé Γöé Swap Γöé Γöé Γöé Γöé Γöé SysLevel Γöé Γöé Γöé Γöé Γöé Userdata Γöé Γöé Γöé Γöé Γöé Volume Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Connections Γöé INTEGER Γöé Server Γöé Average number of connect-Γöé Γöé Γöé Γöé Γöé ions since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé CoProcessor Γöé VARCHAR(7) Γöé Base Γöé Coprocessor chip Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Current_CSD Γöé VARCHAR(7) Γöé SysLevel Γöé Current CSD level Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Current_Directory Γöé VARCHAR(260) Γöé Drive Γöé Current directory of Γöé Γöé Γöé Γöé Γöé drive Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Cylinders Γöé INTEGER Γöé Fixed_Disk Γöé Number of cylinders on Γöé Γöé Γöé Γöé Γöé disk Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Data_Bits Γöé SMALLINT Γöé Serial_Port Γöé Serial port data bit Γöé Γöé Γöé Γöé Γöé settings Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Directory_SearchesΓöé INTEGER Γöé Server Γöé Number of directory Γöé Γöé Γöé Γöé Γöé searches since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Disk Γöé SMALLINT Γöé Fixed_Disk Γöé Fixed disk number Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Disk_Bytes_Read Γöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Disk_Bytes_WrittenΓöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Disk_Id Γöé CHAR(4) Γöé Disk Γöé Physical drive identifier Γöé Γöé Γöé Γöé Γöé (in hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Disk_Reads Γöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Disk_Writes Γöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Diskette Γöé SMALLINT Γöé Diskette Γöé Diskette drive number Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Diskette_Drives Γöé SMALLINT Γöé Base Γöé Number of diskette drives Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Dispatches Γöé INTEGER Γöé Process Γöé Number of dispatches for Γöé Γöé Γöé Γöé Γöé process Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Display Γöé SMALLINT Γöé Base Γöé Display device Γöé Γöé Γöé Γöé Display Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Display_Name Γöé VARCHAR(25) Γöé Display Γöé Display name Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Domain Γöé VARCHAR(15) Γöé Base Γöé Workstation LAN request- Γöé Γöé Γöé Γöé Γöé er's primary domain or Γöé Γöé Γöé Γöé Γöé network number Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Drive Γöé CHAR(1) Γöé Drive Γöé Logical drive letter Γöé Γöé Γöé Γöé SysLevel Γöé Logical drive letter of Γöé Γöé Γöé Γöé Γöé SYSLEVEL file Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Drive_Number Γöé SMALLINT Γöé Volume Γöé Logical drive of volume Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Elapsed_Time Γöé INTEGER Γöé Volume Γöé Elapsed time since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Execution_Time Γöé FLOAT Γöé Process Γöé Process execution time Γöé Γöé Γöé Γöé Γöé (in seconds) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Expansion_Slots Γöé SMALLINT Γöé Model Γöé Number of expansion slots Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé FAT_Sectors_Dirty Γöé INTEGER Γöé Server Γöé Number of FAT sectors Γöé Γöé Γöé Γöé Γöé not written to disk Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé FAT_Sect_Written Γöé INTEGER Γöé Server Γöé Number of FAT sectors Γöé Γöé Γöé Γöé Γöé written to disk Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Bytes_Read Γöé INTEGER Γöé Server Γöé Number of bytes read Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Bytes_WrittenΓöé INTEGER Γöé Server Γöé Number of bytes written Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Creates Γöé INTEGER Γöé Server Γöé Number of files created Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Deletes Γöé INTEGER Γöé Server Γöé Number of files deleted Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Extension Γöé VARCHAR(3) Γöé Component Γöé File extension of Γöé Γöé Γöé Γöé SysLevel Γöé SYSLEVEL file Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Handle Γöé CHAR(4) Γöé Logical_Disk Γöé File handle (in Γöé Γöé Γöé Γöé Γöé hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Opens Γöé INTEGER Γöé Server Γöé Number of file opens Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Name Γöé VARCHAR(260) Γöé Logical_Disk Γöé File name (if available) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Reads Γöé INTEGER Γöé Server Γöé Number of file reads Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Renames Γöé INTEGER Γöé Server Γöé Number of files renamed Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé File_Writes Γöé INTEGER Γöé Server Γöé Number of files writes Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Fixed_Disks Γöé SMALLINT Γöé Base Γöé Number of fixed disks Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Format Γöé VARCHAR(5) Γöé Diskette Γöé Diskette format Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Free Γöé INTEGER Γöé Memory Γöé Memory free for new Γöé Γöé Γöé Γöé Γöé application use (in Γöé Γöé Γöé Γöé Γöé bytes) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Hashing Γöé CHAR(1) Γöé Volume Γöé Volume hashing support Γöé Γöé Γöé Γöé Γöé indicator (Y,N) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Heads Γöé INTEGER Γöé Fixed_Disk Γöé Number of heads Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Interrupt_Level Γöé SMALLINT Γöé Expansion_Slot Γöé Token-Ring Network Γöé Γöé Γöé Γöé Γöé adapter interrupt level Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Interrupt_Time Γöé FLOAT Γöé Process Γöé Time process spent ser- Γöé Γöé Γöé Γöé Γöé vicing interrupts (in Γöé Γöé Γöé Γöé Γöé seconds) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé IO_Address Γöé CHAR(9) Γöé Expansion_Slot Γöé Token-Ring Network Γöé Γöé Γöé Γöé Γöé adapter I/O address range Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Keyboard_Id Γöé CHAR(4) Γöé Base Γöé Keyboard identifier (in Γöé Γöé Γöé Γöé Keyboard Γöé hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Keyboard_Name Γöé VARCHAR(30) Γöé Keyboard Γöé Keyboard name Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Last_Action Γöé VARCHAR(4) Γöé Logical_Disk Γöé Last action on file (for Γöé Γöé Γöé Γöé Γöé example: OPN, CLS) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Last_Written Γöé TIMESTAMP Γöé File Γöé Date and time file was Γöé Γöé Γöé Γöé Γöé last written Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Location Γöé VARCHAR(260) Γöé File Γöé Path of the critical file Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Machine_Name Γöé VARCHAR(30) Γöé Model Γöé Machine name Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Continue on the next page of this chapter. ΓòÉΓòÉΓòÉ 22.6. Data Cross-Reference (continued) ΓòÉΓòÉΓòÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé COLUMN NAME Γöé SQL TYPE Γöé TABLE NAME Γöé DESCRIPTION Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Managing_System Γöé VARCHAR(48) Γöé Base Γöé IBM LAN Requester com- Γöé Γöé Γöé Γöé Γöé puter name or Novell Γöé Γöé Γöé Γöé Γöé NetWare internetwork Γöé Γöé Γöé Γöé Γöé address of managing Γöé Γöé Γöé Γöé Γöé system Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Max_Dir_Slots_UsedΓöé INTEGER Γöé Volume Γöé Maximum number of Γöé Γöé Γöé Γöé Γöé directory slots used for Γöé Γöé Γöé Γöé Γöé this volume Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Model Γöé CHAR(11) Γöé Base Γöé Workstation Γöé Γöé Γöé Γöé Model Γöé model/submodel (in Γöé Γöé Γöé Γöé Γöé hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Mounted Γöé CHAR(1) Γöé Volume Γöé Volume currently mounted Γöé Γöé Γöé Γöé Γöé indicator (Y,N) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Name Γöé VARCHAR(260) Γöé File Γöé File name Γöé Γöé Γöé VARCHAR(6) Γöé Serial_Port Γöé Port name Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Network_Name Γöé VARCHAR(260) Γöé Drive Γöé Alias name of drive Γöé Γöé Γöé Γöé Γöé (format: \\server\alias; Γöé Γöé Γöé Γöé Γöé LAN type only) or network Γöé Γöé Γöé Γöé Γöé name of drive (format: Γöé Γöé Γöé Γöé Γöé fileserver\volume:directorΓöé\subdir; Γöé Γöé Γöé Γöé NETWARE type only) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Node_Address Γöé CHAR(12) Γöé Base Γöé Locally-administered or Γöé Γöé Γöé Γöé Expansion_Slot Γöé universally-administered Γöé Γöé Γöé Γöé Γöé address of primary Token- Γöé Γöé Γöé Γöé Γöé Ring Network adapter (in Γöé Γöé Γöé Γöé Γöé hexadecimal) Γöé Γöé Γöé Γöé Γöé Locally-administered or Γöé Γöé Γöé Γöé Γöé universally-administered Γöé Γöé Γöé Γöé Γöé address of Token-Ring Γöé Γöé Γöé Γöé Γöé Network adapter (in Γöé Γöé Γöé Γöé Γöé hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Node_Type Γöé CHAR(4) Γöé Base Γöé Operating system and Γöé Γöé Γöé Γöé Γöé requester/server type Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Not_Working_Set Γöé INTEGER Γöé Memory Γöé Number of bytes currently Γöé Γöé Γöé Γöé Γöé not in working set Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Operating_System Γöé VARCHAR(80) Γöé Base Γöé Operating system name Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Packets_Received Γöé INTEGER Γöé Server Γöé Number of packets receivedΓöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Packets_Routed Γöé INTEGER Γöé Server Γöé Number of packets routed Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Packets_Transmit Γöé INTEGER Γöé Server Γöé Number of packets Γöé Γöé Γöé Γöé Γöé transmitted since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Parallel_Ports Γöé SMALLINT Γöé Base Γöé Number of parallel ports Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Parity Γöé VARCHAR(5) Γöé Serial_Port Γöé Serial port parity Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Path Γöé VARCHAR(260) Γöé Syslevel Γöé Path of syslevel file Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Peak_Connections Γöé INTEGER Γöé Server Γöé Peak number of connectionsΓöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Peak_Utilization Γöé INTEGER Γöé Server Γöé Peak CPU utilization Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Planar_Id Γöé CHAR(4) Γöé Base Γöé Planar identifier (in Γöé Γöé Γöé Γöé Γöé hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé POS_Data Γöé CHAR(8) Γöé Expansion_Slot Γöé Option Select data bytes Γöé Γöé Γöé Γöé Γöé 1, 2, 3, 4 (in Γöé Γöé Γöé Γöé Γöé hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Port Γöé SMALLINT Γöé Serial_Port Γöé Port number Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Previous_CSD Γöé VARCHAR(7) Γöé SysLevel Γöé Previous CSD level Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Process_Id Γöé CHAR(4) Γöé Logical_Disk Γöé Process identifier (in Γöé Γöé Γöé Γöé Process Γöé hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Process_Name Γöé VARCHAR(8) Γöé Logical_Disk Γöé Process name Γöé Γöé Γöé Γöé Process Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Processor Γöé VARCHAR(7) Γöé Model Γöé Processor chip Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Processor_Speed Γöé SMALLINT Γöé Model Γöé Processor speed (in MHz) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Product_Number Γöé VARCHAR(8) Γöé Base Γöé Workstation product Γöé Γöé Γöé Γöé Γöé number Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Program_Name Γöé VARCHAR(80) Γöé Component Γöé Program name Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Purgable_Blocks Γöé INTEGER Γöé Volume Γöé Number of purgable blocks Γöé Γöé Γöé Γöé Γöé not yet reclaimed Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé RAM_Address_Range Γöé CHAR(11) Γöé Expansion_Slot Γöé Token-Ring Network Γöé Γöé Γöé Γöé Γöé adapter RAM address range Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Reads Γöé INTEGER Γöé Disk Γöé Number of read operations Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Read_Time Γöé FLOAT Γöé Disk Γöé Time required for read Γöé Γöé Γöé Γöé Γöé operations (in seconds) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Record_Locks Γöé INTEGER Γöé Server Γöé Number of recoed locks Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Removable Γöé CHAR(1) Γöé Volume Γöé Volume remove support Γöé Γöé Γöé Γöé Γöé indicator (Y,N) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Report_Date Γöé DATE Γöé Base Γöé Reporting date of vital Γöé Γöé Γöé Γöé Disk Γöé product data or perform- Γöé Γöé Γöé Γöé Logical_Disk Γöé ance data Γöé Γöé Γöé Γöé Memory Γöé Γöé Γöé Γöé Γöé Process Γöé Γöé Γöé Γöé Γöé Swap Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Report_Time Γöé TIME Γöé Base Γöé Reporting time of vital Γöé Γöé Γöé Γöé Disk Γöé product data or perform- Γöé Γöé Γöé Γöé Logical_Disk Γöé ance data Γöé Γöé Γöé Γöé Memory Γöé Γöé Γöé Γöé Γöé Process Γöé Γöé Γöé Γöé Γöé Swap Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Requests Γöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ROM_Address_Range Γöé CHAR(11) Γöé Expansion_Slot Γöé Token-Ring Network Γöé Γöé Γöé Γöé Γöé adapter ROM address range Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Sectors_Per_Block Γöé INTEGER Γöé Volume Γöé Number of 512 byte sectorsΓöé Γöé Γöé Γöé Γöé per block Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Sectors_Per_Cyl Γöé INTEGER Γöé Fixed_Disk Γöé Number of sectors per Γöé Γöé Γöé Γöé Γöé cylinder Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Sectors_Read Γöé INTEGER Γöé Disk Γöé Number of sectors read Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Sectors_Verified Γöé INTEGER Γöé Disk Γöé Number of sectors Γöé Γöé Γöé Γöé Γöé write/verified Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Sectors_Written Γöé INTEGER Γöé Disk Γöé Number of sectors written Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Serial_Ports Γöé SMALLINT Γöé Base Γöé Number of serial ports Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Size Γöé INTEGER Γöé Drive Γöé Device size (in kilo- Γöé Γöé Γöé Γöé Fixed_Disk Γöé bytes) Γöé Γöé Γöé Γöé File Γöé File size (in bytes) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Slot Γöé SMALLINT Γöé Expansion_Slot Γöé Slot number Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Starting_Block Γöé INTEGER Γöé Volume Γöé Starting block for Γöé Γöé Γöé Γöé Γöé this volume. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Status Γöé VARCHAR(8) Γöé Expansion_Slot Γöé Adapter status (ENABLED Γöé Γöé Γöé Γöé Γöé or DISABLED) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Stop_Bits Γöé VARCHAR(4) Γöé Serial_Port Γöé Serial port stop bit Γöé Γöé Γöé Γöé Γöé settings Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Sub_Address Γöé CHAR(4) Γöé Expansion_Slot Γöé POS subaddressing exten- Γöé Γöé Γöé Γöé Γöé sion Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Swap_In_Count Γöé INTEGER Γöé Swap Γöé Number of swap-in events Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Swap_In_Time Γöé FLOAT Γöé Swap Γöé Time spent on swap-in Γöé Γöé Γöé Γöé Γöé events (in seconds) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Swap_Out_Count Γöé INTEGER Γöé Swap Γöé Number of swap-out events Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Swap_Out_Time Γöé FLOAT Γöé Swap Γöé Time spent on swap-out Γöé Γöé Γöé Γöé Γöé events (in seconds) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Time_Interval Γöé INTEGER Γöé Disk Γöé Performance collection Γöé Γöé Γöé Γöé Logical_Disk Γöé interval (in seconds) Γöé Γöé Γöé Γöé Memory Γöé Γöé Γöé Γöé Γöé Process Γöé Γöé Γöé Γöé Γöé Swap Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Total_Blocks Γöé INTEGER Γöé Volume Γöé Total number of blocks Γöé Γöé Γöé Γöé Γöé for this volume Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Total_Dir_Slots Γöé INTEGER Γöé Volume Γöé Total number of directory Γöé Γöé Γöé Γöé Γöé slots for this volume Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Total_Installed Γöé INTEGER Γöé Memory Γöé Total installed memory Γöé Γöé Γöé Γöé Γöé (in bytes) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Total_Memory Γöé INTEGER Γöé Base Γöé Total memory (in kilo- Γöé Γöé Γöé Γöé Γöé bytes) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Total_Sectors Γöé INTEGER Γöé Fixed_Disk Γöé Total number of sectors Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Tracks Γöé SMALLINT Γöé Diskette Γöé Number of tracks Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Transactions Γöé INTEGER Γöé Server Γöé Number of transactions Γöé Γöé Γöé Γöé Γöé since IPL Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Type Γöé SMALLINT Γöé Diskette Γöé Diskette type Γöé Γöé Γöé VARCHAR(8) Γöé Drive Γöé Logical drive type (for Γöé Γöé Γöé Γöé Γöé example: LAN, NETWARE, Γöé Γöé Γöé Γöé Γöé FAT, HPFS) Γöé Γöé Γöé Γöé Γöé bytes) Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Continue on the next page of this chapter. ΓòÉΓòÉΓòÉ 22.7. Data Cross-Reference (continued) ΓòÉΓòÉΓòÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé COLUMN NAME Γöé SQL TYPE Γöé TABLE NAME Γöé DESCRIPTION Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Universal_Address Γöé CHAR(12) Γöé Base Γöé Universally-administered Γöé Γöé Γöé Γöé Expansion_Slot Γöé address of primary Token- Γöé Γöé Γöé Γöé Γöé Ring Network adapter (in Γöé Γöé Γöé Γöé Γöé hexadecimal) Γöé Γöé Γöé Γöé Γöé Universally-administered Γöé Γöé Γöé Γöé Γöé address of Token-Ring Γöé Γöé Γöé Γöé Γöé Network adapter (in Γöé Γöé Γöé Γöé Γöé hexadecimal) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Userid Γöé VARCHAR(48) Γöé Base Γöé Current IBM LAN requester Γöé Γöé Γöé Γöé Γöé logon user ID or Novell Γöé Γöé Γöé Γöé Γöé NetWare login user name Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé User_Data Γöé VARCHAR(3500) Γöé User_data Γöé User supplied data Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Utilization Γöé INTEGER Γöé Server Γöé Average CPU utilization Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé User_Slots Γöé SMALLINT Γöé Model Γöé Number of user slots Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Verifies Γöé INTEGER Γöé Disk Γöé Number of write/verify Γöé Γöé Γöé Γöé Γöé operations Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Verify_Time Γöé FLOAT Γöé Disk Γöé Time required for Γöé Γöé Γöé Γöé Γöé write/verify operations Γöé Γöé Γöé Γöé Γöé (in seconds) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Version Γöé VARCHAR(12) Γöé Base Γöé Operating system version Γöé Γöé Γöé CHAR(4) Γöé SysLevel Γöé SYSLEVEL version Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Video Γöé VARCHAR(4) Γöé Base Γöé Current video adapter Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Video_Memory Γöé INTEGER Γöé Base Γöé Video memory (in kilo- Γöé Γöé Γöé Γöé Γöé bytes) Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Volume Γöé VARCHAR(11) Γöé Drive Γöé Volume label Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Volume_Name Γöé VARCHAR(16) Γöé Volume Γöé Netware volume name Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Volume_Number Γöé SMALLINT Γöé Volume Γöé Netware volume slot numberΓöé Γöé Γöé Γöé Drive Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Working_Set Γöé INTEGER Γöé Memory Γöé Number of bytes currently Γöé Γöé Γöé Γöé Γöé in working set Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Bytes_Rcvd Γöé INTEGER Γöé Server Γöé Number of times Bytes_ Γöé Γöé Γöé Γöé Γöé Received has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Bytes_Trans Γöé INTEGER Γöé Server Γöé Number of times Bytes_ Γöé Γöé Γöé Γöé Γöé Transmitted has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Dbyte_Read Γöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Dbyte_WrittenΓöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Dir_Searches Γöé INTEGER Γöé Server Γöé Number of times Γöé Γöé Γöé Γöé Γöé Directory_Searches wrappedΓöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Disk_Reads Γöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Disk_Writes Γöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Sects_Dirty Γöé INTEGER Γöé Server Γöé Number of times FAT_Sects_Γöé Γöé Γöé Γöé Γöé _Dirty has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_File_Bytes_ Γöé INTEGER Γöé Server Γöé Number of times File_BytesΓöé Γöé Read Γöé Γöé Γöé _Read has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_File_Bytes_ Γöé INTEGER Γöé Server Γöé Number of times File_BytesΓöé Γöé Written Γöé Γöé Γöé _Written has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_File_Creates Γöé INTEGER Γöé Server Γöé Number of times Γöé Γöé Γöé Γöé Γöé File_Creates has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_File_Deletes Γöé INTEGER Γöé Server Γöé Number of times Γöé Γöé Γöé Γöé Γöé File_Deletes has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_File_Opens Γöé INTEGER Γöé Server Γöé Number of times File_OpensΓöé Γöé Γöé Γöé Γöé has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_File_Reads Γöé INTEGER Γöé Server Γöé Number of times File_ReadsΓöé Γöé Γöé Γöé Γöé has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_File_Writes Γöé INTEGER Γöé Server Γöé Number of times Γöé Γöé Γöé Γöé Γöé File_Writes has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_File_Reads Γöé INTEGER Γöé Server Γöé Number of times File_ReadsΓöé Γöé Γöé Γöé Γöé has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Pkts_ReceivedΓöé INTEGER Γöé Server Γöé Number of times Pkts_ Γöé Γöé Γöé Γöé Γöé Received has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Pkts_Routed Γöé INTEGER Γöé Server Γöé Number of times Pkts_ Γöé Γöé Γöé Γöé Γöé Routed has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Pkts_TransmitΓöé INTEGER Γöé Server Γöé Number of times Pkts_ Γöé Γöé Γöé Γöé Γöé Transmitted has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Record_Locks Γöé INTEGER Γöé Server Γöé Number of times Record_ Γöé Γöé Γöé Γöé Γöé Locks has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Requests Γöé INTEGER Γöé Server Γöé Reserved Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Sects_Dirty Γöé INTEGER Γöé Server Γöé Number of times FAT_Sects_Γöé Γöé Γöé Γöé Γöé _Dirty has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Sects_WrittenΓöé INTEGER Γöé Server Γöé Number of times FAT_Sects_Γöé Γöé Γöé Γöé Γöé _Written has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Wrap_Transactions Γöé INTEGER Γöé Server Γöé Number of times Γöé Γöé Γöé Γöé Γöé Transactions has wrapped Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Writes Γöé INTEGER Γöé Disk Γöé Number for write oper- Γöé Γöé Γöé Γöé Γöé ations Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Write_Time Γöé FLOAT Γöé Disk Γöé Time required for write Γöé Γöé Γöé Γöé Γöé operations (in seconds) Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ 23. User Data Area Management ΓòÉΓòÉΓòÉ The user data area management utilities provide extended capabilities for defining and implementing the usage of the user data collected by the LAN Management Utilities/2 from each workstation. By carefully defining the user data to be collected before implementing a LAN Management Utilities/2 database, the effectiveness of LAN management and the productivity of LAN administrators is greatly enhanced. The user data management utilities provide the customer: 1. A methodology to easily define the data to be kept in the USERVPD.DAT file on each workstation and to format the data definition into a useable USERVPD.DAT file. 2. A mechanism to parse the USER_DATA column of the LMU2.USER_DATA table and create (any number of) customer defined Database Manager tables for LAN management. Tables with many different relationships and dependencies can be created and maintained. 3. A method to maintain the custom tables (through scheduled runs of the LMUUDF formatting utility) 4. The ability to track the results of updates to the customer tables by monitoring the SQL LMUUDF_LOG table. ΓòÉΓòÉΓòÉ 23.1. Why User Data Management ΓòÉΓòÉΓòÉ Through the use of the user data management methodology and utilities, customized SQL Tables can be defined with many different kinds of relationships. The type and content of a table is limited only by the amount of data put in the user data definition. Careful planning of the user data can greatly enhance LAN administration, helping operations, configuration, performance, and inventory management. Here are some examples of possible types of tables which can be created and how they might be used. USER_INFO Table This table could contain information about the user of a particular computer. One might include such information as Name, employee number, department, and phone number. This table would give the LAN administrator quick access to information about who to call in case there is a problem with a particular computer. Each piece of information in the table would be assigned to a single data field in USERVPD.CFG file. EQUIPMENT Table This table could contain information about the all the equipment associated with a particular computer. This table would have a many-to-one relationship in that many pieces of equipment could be assigned to one computer. Each row in the table would contain information about one piece of equipment. This would be set up in the USERVPD.CFG file as a data field containing sub-data fields with multiple elements. This table could be used for inventory tracking of computers and peripheral devices. Changes to inventory would be automatically reflected in the data base as user data was updated on each workstation. It can also be used as a tool for configuration management. SOFTWARE Table This table could contain information about all the software used by a particular computer. Each row of the table could contain one piece of software, serial number information, etc. This information would also be set up in the USERVPD.CFG file as a data field containing sub-data fields with multiple elements. This table could be used for inventory tracking of software, software usage indications and possibly trend analysis. It could identify potential performance problems in LAN segments. ΓòÉΓòÉΓòÉ 23.2. Files and Utilities Included ΓòÉΓòÉΓòÉ The files and utilities needed for user data area management include: o A USERVPD.SMP file which defines a typical format for the USER_DATA field. This file is copied to USERVPD.CFG and customized by the customer. o A utility (CVT_VPD.), which runs from both DOS and OS/2, to format the USERVPD.CFG file into the USERVPD.DAT file required by LAN Management Utilities/2. o A utility (LMUUDF.CMD.), which runs on the system where the LAN Management Utilities/2 Database is located, to parse the USER_DATA column of the source table or view and create/update customer defined Database Manager tables. o A sample LMUUDF.SMP file which which gets copied to the LMUUDF.PRO file and defines the IBM Database Manager tables which will be created and updated each time the LMUUDF.CMD application is run. ΓòÉΓòÉΓòÉ 23.3. Customizing User Data ΓòÉΓòÉΓòÉ Customizing user data has two main tasks for you to execute: 1. Determine the data requirements 2. Create the USERVPD.CFG file. The USERVPD.CFG file is used to create the USERVPD.DAT file that is read by the LMU/2 QDOSVPD and QUERYVPD programs. Return to the Table of Contents and select the next topic. ΓòÉΓòÉΓòÉ 23.3.1. Determining User Data Requirements ΓòÉΓòÉΓòÉ The first step to customization is to define the installation dependent data requirements. Table "Sample USER_DATA format" shows a sample of how data fields can be defined for user data requirements. It is up to the customer to decide what data and formats are required for his specific needs. It is recommended that a table similar to the sample provided be generated to make the process of customization as easy as possible and to determine if the data elements chosen meet the installations requirements. Table "USER_DATA format worksheet" is included to help in the task of generating a customized user data area. This worksheet should be completed prior to creating the USERVPD.CFG file. Reproduce the pages as needed for more complex user data requirements. ΓòÉΓòÉΓòÉ 23.3.2. Creating and Customizing the USERVPD.CFG File ΓòÉΓòÉΓòÉ The USERVPD.SMP file included with LAN Management Utilities/2 is an example of what a USERVPD.CFG file should look like. This USERVPD.CFG file provides the basic format that each managed workstation will use for creating its USERVPD.DAT file. The following steps should be followed to create and customize the USERVPD.CFG file: 1. Copy the USERVPD.SMP file to the USERVPD.CFG file. This creates a base USERVPD.CFG file to customize. 2. If the fields defined in this file are sufficient to satisfy the needs for this installation, then the USERVPD.CFG customization is complete. Proceed to The USERVPD.DAT File. 3. With your favorite editor, edit the USERVPD.CFG file. Change the file to agree with currently defined requirements. Be sure to adhere to the file format definition in Rules for defining the USERVPD.CFG file. 4. Save the updated USERVPD.CFG file ΓòÉΓòÉΓòÉ 23.3.2.1. Rules for Defining the USERVPD.CFG File ΓòÉΓòÉΓòÉ The rules for defining the USERVPD.CFG file are quite simple, but must be followed in order to produce the appropriate USERVPD.DAT file for this installation. Refer to Sample USERVPD.CFG file (USERVPD.SMP.) for an example of a USERVPD.CFG file. ----------Rules for defining the USERVPD.CFG file---------- Data Fields 1. A `data field', which will translate to a column in Database manager, is delimited by brackets, i.e. [] o A `[' character signifies the start of a data field o A `]' character signifies the end of a data field [data field] 2. There may more than one `data field' per line e.g. [data field 1] [data field 2] [... ] 3. A `data field' may span more than one line [This is a fairly long data field which might be a comment field and will span more than one line of the USERVPD.CFG file] 4. A data field may contain 1 or more `Sub-data' fields each delimited by braces, i.e. {}. [{Sub-data field 1}{Sub-data field 2}{...}{Sub-data field n}] 5. Any other data in the file (outside of the []s or {}s) is considered comments and is ignored when the conversion is done to create the USERVPD.DAT file. Sub-data Fields 1. A `Sub-data field' is a field within a `data field' and is delimited by braces, i.e. {}. A sub-data field is made up of from 1 to n elements delimited by commas. {element 1,element 2,...,element n} 2. Each element of a sub-data field translates to a column in an SQL table. Since multiple sub-data fields may be present in a data field, each sub-data field translates to one row of an SQL table. The elements are numbered using the data field number followed by a `.' and the element number. For example, if data field 15 had sub-data fields with multiple elements, they would be numbered like the following: [{15.1,15.2,...,15.n}{15.1,15.2,...15.n}{etc}] 3. Not all elements need to be present in a sub-data field and those not found will be set to NULL in the SQL table. i.e. If a sub-data field was defined to contain 6 elements and only 4 were present, the last 2 would be set to NULL. 4. A NULL element in a sub-data field is represented in the following example: {element 1,,element 3,...} ---------- By following these rules it is quite simple to build up a default system installation USERVPD.CFG file to be used as a template for each managed workstation. It is recommended that each `data field' described in the USERVPD.CFG file be numbered since this number will be used later in the definition of the formatting profile LMUUDF.PRO.. ΓòÉΓòÉΓòÉ 23.3.3. The USERVPD.DAT File ΓòÉΓòÉΓòÉ Data from the USERVPD.DAT file is transported to the managing system and put into the LAN Management Utilities/2 database each time a QUERYVPD or QDOSVPD command is executed. The CVT_VPD utility formats the USERVPD.CFG file into a USERVPD.DAT file that is a condensed version with all comments stripped off and only required data remaining. (See Example USERVPD.DAT file for an example of what a formatted USERVPD.DAT file would look like) The format of the conversion command is: drive:\path\CVT_VPD sourcedrive\sourcepath\sourcefilename targetdrive:\targetpath\targetfilename The CVT_VPD utility is a family application that will run in both DOS and OS/2. The only parameters to specify are the source file and target file. CVT_VPD looks for the source USERVPD.CFG file in the current directory first and then the Root directory (C:\). It always creates the USERVPD.DAT file in the root directory. The USERVPD.DAT file can be automatically created for each workstation from USERVPD.CFG when LMUCUST is run. Some preliminary work needs to be performed by the LAN administrators for creating customized USERVPD.CFG for each workstation, or a general form of USERVPD.CFG can be created and customization performed on the workstation after installing LMU/2. ΓòÉΓòÉΓòÉ 23.4. Customizing the Formatting Profile ΓòÉΓòÉΓòÉ The user data formatting profile (default name is LMUUDF.PRO.) is the key element for describing the individual SQL tables that will be maintained by the formatting utility. (Refer to Example LMUUDF.PRO file for a sample LMUUDF.PRO.) The profile must be customized to agree with the format defined for the SQL USER_DATA column data. Since the USERVPD.CFG file has already been built based on the user data requirements, it will be used to help define the formatting profile. The user data formatting profile defines the following: 1. The information needed to generate the SQL query. 2. The number of tables to be generated from the user data 3. The type of SQL table (one-to-one, many-to-one, etc) 4. The definition of each one of the tables (i.e column names, types, lengths, and referential integrity) 5. The source of the data to be put in the tables, which can be either: a. The `data field' or `sub-data field' number as it applies to the parsed USER_DATA column of the LMU2.BASE table b. A SQL column from the source table or view 6. The date and time of the last run of the formatting utility There is no limit on the number of profiles that can be created. Each profile must follow the customization rules. Since LMUUDF only processes one profile at a time, defining more than one profile requires multiple invocations of LMUUDF. with each profile. See LMUUDF.PRO Customization Rules for the rules on building an LMUUDF profile. ΓòÉΓòÉΓòÉ 23.4.1. LMUUDF.PRO Customization Rules ΓòÉΓòÉΓòÉ 1. The first record of the file is the header record where the date and time stamps are kept. This record is updated each time the program is run. The date is always assigned to the variable "last_run_date" and the time is always assigned to the variable "last_run_time". These variables can be used in the where_vars keyword as part of an SQL query. Date must be specified in the format mm-dd-yyyy. Time must be specified in the format hh:mm:ss. 2. Any lines beginning with an asterisk (*) are considered comments and are ignored. 3. If the line is in the format "variable: [value]" it is assumed to be a "variable" being set to "value". Certain variables are considered Keywords by the utility. Keywords are: Keyword Description data_base The name of the Database Manager database where the table containing the source data resides (default = LMU2.) base_table The name of the table or view in data_base where the source data will be extracted (default = LMU2.CONFIG) table_qualifier The userid of the person who created the base_table (default = `' (NULL) which means LMUUDF must be run from the same user who created the tables in the first place) parse_column The name of the column containing the source data in the base_table This can be any column of data which follows the rules for defining user data (See Rules for defining the USERVPD.CFG file) key_column The column name used in all the tables as the `key' column. (default = COMPUTER) This parameter is used as the default primary key for all tables unless overridden on the :Table tag when a new table is defined. This keyword is always used in every SQL query for all tables to determine common data records. where_clause Any valid SQL `WHERE' clause that can be executed against the base_table. (default = [report_date > ? or (report_date = ? and report_time > ?]) This clause must follow the rules for describing and preparing dynamic SQL statements for execution and can contain no host variables, only parameter markers (?). where_vars The names of the variables which will replace the `?' in the "where_clause". (default = [last_run_date last_run_date last_run_time]) log_inserts A variable that can be set to [YES] or [1] to turn on logging for all records that are inserted into the SQL tables. Normally only updates to records are logged. (default = [NO]) This allows tracking of new records added to the tables defined in the profile. normal_rc The return code issued by LMUUDF when it terminates with from a `normal' parse with no warning indications. (default = 0). warn_rc The return code issued by LMUUDF when it terminates with warning messages. (default = 1). error_rc The return code issued by LMUUDF when it terminates with error messages. (default = -1). :Table This is a special tag (not in key word format) which indicates the start of a new table description and is explained in detail in Defining a Table with the :Table Tag ΓòÉΓòÉΓòÉ 23.4.2. Defining a Table with the :Table Tag ΓòÉΓòÉΓòÉ The ":Table" key word is used to describe the beginning of an SQL table definition. The general form of the :Table tag is: :Table name[x] key[x] override[x] refc[x] set[x] clear[x] Multiple :Table tags may be specified for a table but the first one must contain the name[table name] tag to identify the table. Succeeding records may contain any options for the table. Tag values are not case sensitive. :Table name[table name] key[column<,column>] :Table override[column] refc[Foreign Key] :Table set[column] clear[column<,column> or "DELETE"] The :Table tag parameters define each SQL table to be created/updated and are interpreted as follows: Parameter Description name The SQL name of the table to be created/updated. This is a required parameter and there is no default. Only one table name per :Table tag is allowed. key The name of the SQL primary key to be associated with the table. The default is obtained from the key_column keyword defined at the beginning of the profile. If the primary key is different from the key_column on a multivalued table, then the key_column is used in the SQL search of the table for common records and the primary key is used to guarantee uniqueness. The Primary key may contain multiple values separated by commas. Caution should be exercised when defining primary key column names that are the names of columns created from data in the parsed data area. This is due to the fact that SQL requires that primary key columns must contain data. It is up to the user to guarantee the user data is not null for primary key columns. Warning messages will be generated and data records will not be put into tables when it is determined that the primary key would be null. override The SQL column name of the management override column in the table. The default is set to the value of the "mgmt_override" keyword (defined at the beginning of the profile). The management override column is checked before any record is updated and the record is not updated if the column contains a value (i.e. The column is NOT null) This is extremely handy for administrators. Typically the field is defined as an 8 character field and the LAN administrator can place his userid in the record to prevent it from being updated. refc The SQL referential constraints and delete rules for the table. (default = Refc[NULL]) Any valid SQL constraints and rules may be specified here following SQL conventions. The field is used exactly as specified. set The SQL name of a one character column defined in a multivalued table which will get set to an "X" if a record is determined to be no longer required in the user data. (default = Set[NULL]) The column name must be declared in the table definition for the table. This provides the means for tracking changes to equipment, software, etc assigned to a workstation. When a piece of equipment or software is removed, the record will automatically be marked with an "X" in the SET column because it no longer appears in the user data. Records marked with an "X" can be tracked with a simple SQL query. clear The SQL name (or names separated by commas) of columns in a multivalued table that will be set to NULL if a record is determined to be no longer required in the user data. (default = Clear[NULL]) If the name is the keyword "DELETE" (Clear[DELETE]) then no fields are cleared and the record is deleted from the table. All lines following the :Table tag are assumed to specify SQL database create and update information for the table. They have a positional parameter format of which the first four are required, otherwise they have the following (free) format: Column Source Type Length Description The parameters are interpreted as follows: Parameter Description Column The destination column name within the SQL table defined by the previous :table tag. Source The source of where the data is coming as follows: o If the Source field is numeric, such that the table column definition looks like: Column Source Type Length Description SERIAL_NO 1 CHAR 12 Computer Serial Number then it specifies the number of the data field {or sub-data field element} associated with the parsed data from the parse_column column. [1][2][{3.1,3.2,...,3.n}{3.1,3.2,...,3.n}][...][n] o If the Source is character, such that the table column definition looks like: Column Source Type Length Description COMPUTER COMPUTER VARCHAR 15 Computer name from the SQL table then it specifies the column name in the source table or view where the data is extracted. i.e. Any other column defined in the source table or view can be extracted and placed in the destination table. If the keyword `NULL' is specified in place of a column name, Column Source Type Length Description LOCKED NULL CHAR 8 Management Override field then it means no data will be extracted from SQL or the parse_column and placed in the destination column. It indicates the data may come from another source (i.e. manual input, etc). The column still needs to be specified in the profile even though the data comes from elsewhere in order for the table to be properly created. This is handy for defining management override fields and comment fields which are filled in by an administrator. Type Specifies the Database Manager type for the COLUMN. This is used to format the table updates and for creating the TABLE if it does not exist. It MUST BE a valid Database Manager datatype (i.e. CHARACTER, CHAR, VARCHAR, DATE, TIME, TIMESTAMP, SMALLINT, INTEGER, INT, DECIMAL, DEC). LONG VARCHAR and GRAPHIC datatypes are not supported. Length The (maximum) length of the data for the COLUMN. It also specifies the length of the Database Manager column when a CREATE TABLE is done to create the table if it does not already exist. The LENGTH may be enclosed in parenthesis if desired. Description The description of the line (optional) ΓòÉΓòÉΓòÉ 23.5. Invoking the LMUUDF formatting utility ΓòÉΓòÉΓòÉ Once all the required support files have been created and there is data in the source table on the managing workstation, LMUUDF can be run. LMUUDF must be run on the workstation where the LMU/2 database resides. The general format of the command to invoke LMUUDF is: drive:\path\LMUUDF drive:\path\profilename The LMUUDF utility uses the following defaults when it is invoked: path C:\LMU2 profilename LMUUDF.PRO These can be overridden at execution time by specifying the complete path and profile name. In this way any profile can be used by LMUUDF. ΓòÉΓòÉΓòÉ 23.5.1. Scheduling LMUUDF ΓòÉΓòÉΓòÉ The most effective way of executing the user data formatter is through scheduled runs of the application. This can be accomplished in several ways: o Manually invoke LMUUDF at periodic intervals. o Turn on the LMU/2 alert capability that generates an alert each time the database is changed. Create an application that gets invoked from the alerts table to start LMUUDF. LMUUDF will process the database according to the profile rules. o Place an entry in the LMU/2 scheduler file to invoke LMUUDF at periodic intervals during the day or week. See LMUUDG Program Operation for information on how the formatter processes data from the source table. ΓòÉΓòÉΓòÉ 23.5.2. LMUUDF Program Operation ΓòÉΓòÉΓòÉ The following scenario describes briefly how the formatter processes the data from the source table: 1. See if the user data formatter profile exists. If it doesn't the program cannot continue. Display a message indicating the profile must be built before continuing. 2. Read the user data formatter profile: o Obtain the header line to determine date and time the database was last processed. o Process the lines which set variables and key word variables that might override those defaults in the application. o Determine the tables to be created or updated 3. Register the Database Manager functions and start the background process. 4. Connect to the proper database (default=LMU2.) 5. Build a Database Manager user data query to pull the required fields out of each user data record using the "where_clause" and "where_vars" default SQL statements or overrides from the profile. 6. Check the destination table(s) (and the LMUUDF_LOG table) to make sure they exist and create them if they don't. 7. Run the query to retrieve all the records updated since the last time the user data was processed. If no records are found, the program is complete. 8. Do for each record retrieved from the user data query: a. Parse the user data into the proper data (and sub-data) fields. b. Verify that the user data fields are correct for each column in the destination table. c. Build a Database Manager add, update or delete transaction for each record of each table. d. Write new data to the Database Manager output table. 9. Perform necessary Database Manager clean-up and shutdown operations. 10. If all data was processed successfully, update the profile header timestamp to indicate when the processing was completed. ΓòÉΓòÉΓòÉ 23.6. Sample files ΓòÉΓòÉΓòÉ This section contains samples of the files involved in creating formatted user data that can be included in the LMU/2 database and extracted with SQL queries. Sample USERVPD.CFG file Example USERVPD.DAT file Example LMUUDF.PRO file ΓòÉΓòÉΓòÉ 23.6.1. Sample USERVPD.CFG file (USERVPD.SMP.) ΓòÉΓòÉΓòÉ 1) ^Assigned_user ^[Last, First ] 2) ^User Serial # ^[123456] 3) ^User department # ^[XXX] 4) ^User Internal Phone # ^[555-5555] 5) ^User External Phone # ^[555-555-5555] 6) ^Building ^[1111] 7) ^Floor ^[001] 8) ^Location Office # ^[XXXX] 9) ^Location Internal Phone # ^[555-5555] 10)^Location External Phone # ^[555-555-5555] 11)^Owning_Manager ^[Last, First ] 12)^Owning_Department ^[XXX] 13)^T/R Port ID ^[XXXXXXXXXX] 14)^Power Outlet ^[XXXXXXX] 15)^Equipment ^Format:^{Machine_Type,Model,Serial_Number,Date_Installed} ^--------------------------------------------------------- ^[Start of equipment ^^{IBM-8580,001,23-1234567,09-01-1992} ^System unit ^^{IBM-8514,001,00-1097175,09-01-1992} ^Display ^^{IBM-8513,001,23-CLV46,09-01-1992} ^Display ^^{IBM-1391401,,4655517,09-01-1992} ^Keyboard ^^{IBM-90X6778,,1306518,09-01-1992} ^Mouse ^^{IBM-4216,031,41-8886A,09-01-1992} ^Printer ^^{IBM-6180,,B1506,09-01-1992} ^Plotter ^End of equipment] ΓòÉΓòÉΓòÉ 23.6.1.1. Example USERVPD.DAT file ΓòÉΓòÉΓòÉ This file is generated from the USERVPD.CFG file by running the CVT_VPD utility. Note: This file is actually one contiguous record but is shown here as multiple records to allow it to fit on the page or display. [Last, First][123456][XXX][555-5555][555-555-5555][1111][001][XXXX][555-5555][555-555-5555] [Last, First][XXX][XXXXXXXXXX][XXXXXXX] [{IBM-8580,001,23-1234567,09-01-1992}{IBM-8514,001,00-1097175,09-01-1992} {IBM-8513,001,23-CLV46,09-01-1992}{IBM-1391401,,4655517,09-01-1992} {IBM-90X6778,,1306518,09-01-1992}{IBM-4216,031,41-8886A,09-01-1992} {IBM-6180,,B1506,09-01-1992}] ΓòÉΓòÉΓòÉ 23.6.2. Example LMUUDF.PRO file ΓòÉΓòÉΓòÉ Last_run_date: [12-24-1991] Last_run_time: [08:00] /* Last Run Date/Time */ *-------------------------------------------------------------------------------------------------------- *data_base: ^[LMU2] *base_table: ^[CONFIG] *key_column: ^[COMPUTER] *parse_column: ^[USER_DATA] mgmt_override: ^[LOCKED] *log_inserts: ^[YES] *table_qualifier: ^[] *normal_rc: ^[0] *warn_rc: ^[1] *error_rc: ^[-1] *where_clause: ^[report_date > ? or (report_date = ? and report_time > ?)] *where_vars: ^[last_run_date last_run_date last_run_time] *-------------------------------------------------------------------------------------------------------- :Table name[parsed_data] key[computer] * *Column ^Source ^ Type ^Length ^Description *---------------------^--------------------^---------------^----------^-------------------------------------------- COMPUTER ^COMPUTER ^VARCHAR ^21 ^Computer Name (from CONFIG view) LOCKED ^NULL ^VARCHAR ^ 8 ^Management Override field CHANGE_DATE ^REPORT_DATE ^DATE ^ - ^Date Record Updated (from CONFIG view) CHANGE_TIME ^REPORT_TIME ^TIME ^ - ^Time Record Updated (from CONFIG view) ASSIGNED_USER ^1 ^VARCHAR ^20 ^Equipment User's name USER_SERIAL ^2 ^CHAR ^ 6 ^User's Serial # USER_DEPT ^3 ^CHAR ^ 3 ^Equipment User's Department # USER_INT_PHONE^4 ^CHAR ^ 8 ^User's Internal Phone # USER_EXT_PHONE^5 ^CHAR ^12 ^User's External Phone # BUILDING ^6 ^CHAR ^ 4 ^Building equipment is located FLOOR ^7 ^CHAR ^ 3 ^Floor equipment is located LOCATION ^8 ^CHAR ^ 4 ^Office# or Other location of equip. LOC_INT_PHONE ^9 ^CHAR ^ 8 ^Phone # at equipment Location (Internal) LOC_EXT_PHONE ^10 ^CHAR ^12 ^Phone # at equipment Location (External) OWNING_MGR ^11 ^VARCHAR ^20 ^Equipment Owner Manager's name OWNING_DEPT ^12 ^CHAR ^ 3 ^Equipment Owner Department # PORT_ID ^13 ^CHAR ^10 ^Port Identification (Wall Plate) TR_UADDR ^UNIVERSAL_ADDRESS ^CHAR ^12 ^Token Ring universal address (from CONFIG view) MSAU_ID ^NULL ^VARCHAR ^12 ^Multi Station Access Unit ID (manual input) POWER_SOURCE ^14 ^CHAR ^ 7 ^Power Source (Breaker/Panel) EQUIPMENT ^15 ^VARCHAR ^500 ^Equipment assigned to this computer (list) * :Table name[user_info] key[computer] COMPUTER ^COMPUTER ^VARCHAR ^21 ^Computer Name (from CONFIG view) CHANGE_DATE ^REPORT_DATE ^DATE ^ - ^Date Record Updated (from CONFIG view) LOCKED ^NULL ^VARCHAR ^ 8 ^Management Override field ASSIGNED_USER ^1 ^VARCHAR ^20 ^Equipment User's name USER_SERIAL ^2 ^CHAR ^ 6 ^User's Serial # USER_DEPT ^3 ^CHAR ^ 3 ^Equipment User's Department # USER_INT_PHONE^4 ^CHAR ^ 8 ^User's Internal Phone # USER_EXT_PHONE^5 ^CHAR ^12 ^User's External Phone # * :Table name[owner] override[] COMPUTER ^COMPUTER ^VARCHAR ^21 ^Computer Name (from CONFIG view) OWNING_MGR ^11 ^VARCHAR ^20 ^Equipment Owner Manager's name OWNING_DEPT ^12 ^CHAR ^ 3 ^Equipment Owner Department # DEPT_NAME ^NULL ^VARCHAR ^40 ^Equipment Owner Department name * :Table name[TR_STUFF] TR_UADDR ^UNIVERSAL_ADDRESS^CHAR ^12 ^Token Ring universal address COMPUTER ^COMPUTER ^VARCHAR ^21 ^Computer Name (from CONFIG view) PORT_ID ^13 ^CHAR ^10 ^Port Identification (Wall Plate) MSAU_ID ^NULL ^VARCHAR ^12 ^Multi Station Access Unit ID * :Table name[equipment] :Table key[machine_type,serial_no] SET[alert] clear[computer] COMPUTER ^COMPUTER ^VARCHAR ^21 ^Computer Name (from CONFIG view) LOCKED ^NULL ^VARCHAR ^ 8 ^Management Override field MACHINE_TYPE ^15.1 ^VARCHAR ^12 ^Machine Type MODEL ^15.2 ^VARCHAR ^ 3 ^Model number SERIAL_NO ^15.3 ^VARCHAR ^12 ^Machine serial number INSTALL_DATE ^15.4 ^DATE ^ - ^Date machine installed INFO ^NULL ^VARCHAR ^80 ^Comments ALERT ^NULL ^CHAR ^1 ^Alert Action Required flag ΓòÉΓòÉΓòÉ 23.6.3. Sample USER_DATA Format ΓòÉΓòÉΓòÉ The format of the LAN Management Utilities/2 USER_DATA field must be defined by each customer. This gives the opportunity to define and collect information specific to each customer`s requirements. The following USER_DATA format is provided as a guide in defining a customer-specific USER_DATA area. ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Sample USER_DATA format Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓöéFIELDΓöéLENGTHΓöé FORMAT Γöé COLUMN NAME Γöé DESCRIPTION Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 1 Γöé 20 Γöé Last, First Γöé ASSIGNED_USER Γöé Equipment user's name Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 2 Γöé 6 Γöé nnnnnn Γöé USER_SERIAL Γöé User's Serial # Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 3 Γöé 3 Γöé nnn Γöé USER_DEPT Γöé User's department # Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 4 Γöé 8 Γöé nnn-nnnn Γöé USER_INT_PHONEΓöé User's Phone # (Internal) Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 5 Γöé 12 Γöé nnn-nnn-nnnnΓöé USER_EXT_PHONEΓöé User's Phone # (External) Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 6 Γöé 4 Γöé nnnn Γöé BUILDING Γöé Building where equipment is located Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 7 Γöé 3 Γöé nnn Γöé FLOOR Γöé Floor where equipment is located Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 8 Γöé 4 Γöé nnnn Γöé LOCATION Γöé Office # or location of equipment Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 9 Γöé 8 Γöé nnn-nnnn Γöé LOC_INT_PHONE Γöé Phone # at equipment location (Internal)Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 10 Γöé 12 Γöé nnn-nnn-nnnnΓöé LOC_EXT_PHONE Γöé Phone # at equipment location (ExternalΓöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 11 Γöé 20 Γöé Last, First Γöé OWNING_MGR Γöé Equipment owner manager's name Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 12 Γöé 3 Γöé nnn Γöé OWNING_DEPT Γöé Department # owning equipment Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 13 Γöé 10 Γöé nnnn-nn-nn Γöé PORT_ID Γöé Equipment connection Port ID Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 14 Γöé 7 Γöé nnnn-nn Γöé POWER_SOURCE Γöé Power Source location (Panel-Breaker) Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15 Γöé 500 Γöé na Γöé EQUIPMENT Γöé Computer Equipment (1-n). This is a Γöé Γöé Γöé Γöé Γöé Γöé data field containing Sub-data fields Γöé Γöé Γöé Γöé Γöé Γöé and is described in the Sub-data table Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Continue to Equipment Sub-data field format example. ΓòÉΓòÉΓòÉ 23.6.3.1. EQUIPMENT Sub-data field format example ΓòÉΓòÉΓòÉ The following table describes the format of the EQUIPMENT data field in the previous table. Note this definition is repeated to show that a data field may contain any number of sub-data elements, each one identical. It really only needs to be defined once. ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé EQUIPMENT Sub-data field format Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓöéFIELDΓöéLENGTHΓöé FORMAT Γöé COLUMN NAME Γöé DESCRIPTION Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.1Γöé 12 Γöé mfg-mach-type Γöé MACHINE_TYPE Γöé #1 Manufacturer and Machine type Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.2Γöé 3 Γöé model Γöé MODEL Γöé #1 Model number Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.3Γöé 12 Γöé nn-nnnnnnnnn Γöé SERIAL_NO Γöé #1 Machine Serial Number Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.4Γöé 10 Γöé mm-dd-yyyy Γöé INSTALL_DATE Γöé #1 Installation date Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.1Γöé 12 Γöé mfg-mach_type Γöé MACHINE_TYPE Γöé #2 Manufacturer and Machine type Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.2Γöé 3 Γöé model Γöé MODEL Γöé #2 Model number Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.3Γöé 12 Γöé nn-nnnnnnnnn Γöé SERIAL_NO Γöé #2 Machine Serial Number Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.4Γöé 10 Γöé mm-dd-yyyy Γöé INSTALL_DATE Γöé #2 Installation date Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ... Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.1Γöé 12 Γöé mfg-mach_type Γöé MACHINE_TYPE Γöé #n Manufacturer and Machine type Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.2Γöé 3 Γöé model Γöé MODEL Γöé #n Model number Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.3Γöé 12 Γöé nn-nnnnnnnnn Γöé SERIAL_NO Γöé #n Machine Serial Number Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 15.4Γöé 10 Γöé mm-dd-yyyy Γöé INSTALL_DATE Γöé #n Installation date Γöé Γöé Γöé Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ 23.7. LMUUDF_LOG Table ΓòÉΓòÉΓòÉ The1 LMUUDF_LOG table is automatically created the first time LMUUDF is executed. The SQL statement executed to create the table is the following: CREATE TABLE table qualifier.LMUUDF_LOG (COMPUTER VARCHAR(21) EVENT_DATE DATE (-) EVENT_TIME TIME (-) TABLE_NAME VARCHAR(18) PRIMARY_KEYS VARCHAR(80) UDF_CODE CHAR (8) UDF_MESSAGE VARCHAR(80) SQL_CODE CHAR (8) SQL_MESSAGE VARCHAR(400) SQL_COMMAND VARCHAR(400)) The LMUUDF_LOG table keeps track of the activities on the user data. Normally only updates to the records in the table are tracked as well as problems that may be encountered due to invalid data in the user data records. New records which are inserted into the LMUUDF maintained databases can also be tracked by setting the `log_inserts' flag in the LMUUDF.PRO profile. The following is a description of the columns in the LMUUDF_LOG table: Column Name Description COMPUTER The COMPUTER column from the source table or view EVENT_DATE The date of the current run of LMUUDF EVENT_TIME The time of the current run of LMUUDF TABLE_NAME The name of the table currently being accessed PRIMARY_KEYS The primary keys of the table currently being accessed UDF_CODE The LMU/2 message ID if one is present for this log entry UDF_MESSAGE The LMU/2 message if one is present for this log entry SQL_CODE The SQL return code if one is present for this log entry SQL_MESSAGE The SQL message associated with the SQL_CODE if one is present for this log entry SQL_COMMAND The SQL command being executed at the time this entry was made. ΓòÉΓòÉΓòÉ 23.8. USER_DATA Format Worksheets ΓòÉΓòÉΓòÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé USER_DATA format worksheet Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ ΓöéFIELDΓöéLENGTHΓöé FORMAT Γöé COLUMN NAME Γöé DESCRIPTION Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ 24. Alert Generation and Routing ΓòÉΓòÉΓòÉ This appendix discusses the generic alert creation capability in the LAN Management Utilities/2. The generic alert building and routing functions supply a simple interface to create a basic generic alert from user programs written in REXX or the C language. Continue with Alert Generation and Routing ΓòÉΓòÉΓòÉ 24.1. Generic Alert Generation ΓòÉΓòÉΓòÉ This section discusses the AUEUSRGA, AUEREXGA, and AUEDOSAL interfaces and the ability to create generic alerts from user applications. As a part of the fault manager component of LAN Management Utilities/2, you received two modules that will help you to create your own generic alerts from application programs you write in the C language: AUEUSRGA.DLL AUEPITCH.EXE Two additional modules have been provided, one that provides a REXX interface to the alert generation facilities, and a sample REXX CLIST that demonstrates this capability: AUEREXGA.DLL AUEREX01.CMD Another module has been provided that provides user alert generation in a DOS machine: AUEDOSAL.COM The modules, their functions, and their usage are described in the sections that follow. Continue with Alert Generation and Routing ΓòÉΓòÉΓòÉ 24.1.1. AUEUSRGA.DLL ΓòÉΓòÉΓòÉ AUEUSRGA.DLL provides a simple interface from user application programs written in the C language for alert generation. The C function prototype for AUEUSRGA is: unsigned short pascal far _loadds AUEUSRGA (unsigned short, char far *, char far *, char far *); The statement in the user program is of the form: rc = AUEUSRGA(Error_Number, Appl_ID, Message, Event_CPU); Parameter Meaning rc Return code. Unsigned short integer. On return from AUEUSRGA, the return code has these meanings: Value Meaning 0 Success. The parameters received were syntactically correct and AUEUSRGA successfully delivered to AUEPITCH the request to build and ship the generic alert to AUECATCH. 8 Failure. In the case of a failure, consult the LMU/2 messages log file for a detailed explanation. Note: If the return code received from AUEUSRGA is 0 (the request had correct syntax and was successfully delivered to AUEPITCH) but the generic alert seems not to flow from AUEPITCH to AUECATCH, you will need to check the LMU/2 message log to determine if AUEPITCH encountered errors in its processing. Error_Number An unsigned short integer that identifies the type of generic alert you want built. See the error number mappings table in topic Error_Number Mappings for valid values and the generic alert that will be built. Appl_ID A pointer to an ASCIIZ string that contains the name of the user program requesting that the alert be built and shipped. This string has a maximum length of 8 bytes and will be displayed at the NetView console (Hardware Monitor Alerts Dynamic and Alert Detail screens). In the event that you want to drive an automation routine from this alert via the fault manager, be careful to make the first 7 bytes unique, as only 7 characters are allowed in the alerts table entry for Software Product Name (see User-Defined Table for details on the alerts table). Message A pointer to an ASCIIZ string of free-format text that you want displayed at the NetView console (Alert Details panel). The text may also be passed to an automation routine by specification of the proper SV_Parm in the alerts table file (see User-Defined Table for details on the alerts table). Note: Because the LMU/2 command transport initiates the automation routine using the standard OS/2 command line interface, any special symbols in the message string may be misinterpreted by the OS/2 command shell (< and > become redirection, | becomes a pipe, and so forth). To use the symbols as literal symbols, place a double quote in the alerts table Command field as directed in topic Command. The text has a maximum length of 44 characters. This text is included as a Detailed Data Subfield (X'82') in the User Causes (X'94') or Failure Causes (X'96') Subvector of the alert. Event_CPU This is either a zero pointer or the pointer to an ASCIIZ string that identifies the machine on which the fault condition exists. If the machine is an IBM LAN Requester, the string can be up to 8 bytes in length and contains the COMPUTERNAME from the IBMLAN.INI file in the machine. If the machine is a Novell NetWare Requester, the string can be up to 22 bytes in length and contains the Novell internetwork address of the machine. For an IBM LAN Requester, a non-zero pointer causes the Resource Hierarchy subvector to be built with an additional (third) field indicating that the machine raising the alert is different from the machine on which the fault condition exists. For a Novell NetWare Requester, a non-zero pointer causes the Resource Hierarchy List to contain the name NOVELL and causes the Single MAC Address to contain the node address from the Novell internetwork address. Example: rc=AUEUSRGA(21,"MYAPPL","MYERR001 User Data",NULL); In order to call AUEUSRGA from your C language application program, you will need to include the following statement in the .DEF file for your program: IMPORTS AUEUSRGA.AUEUSRGA Continue with Alert Generation and Routing ΓòÉΓòÉΓòÉ 24.1.2. AUEPITCH.EXE ΓòÉΓòÉΓòÉ AUEPITCH must be executing in the machine that is requesting the creation of a generic alert (not necessarily the machine that has the condition). Its function is to accept the alert request from AUEUSRGA or AUEREXGA, determine the transport method to be used (NETBIOS if IBM LAN Requester, or SPX if Novell Requester), and send the alert request via the transport to AUECATCH. Continue with Alert Generation and Routing ΓòÉΓòÉΓòÉ 24.1.3. AUEREXGA.DLL ΓòÉΓòÉΓòÉ AUEREXGA.DLL provides an interface for alert generation from user application programs written in the REXX language. You register this routine as an external function in your REXX program. Its function is to accept the parameters passed from your REXX program and build them into a call to the AUEUSRGA.DLL routine. The interface is much like that documented for AUEUSRGA, except that the parameters are passed as strings. The fourth parameter, indicating the Event_CPU, is optional. RString = AUEREXGA('Error_Number', 'Appl_ID', 'Message', 'Event_CPU') Parameter Meaning RString A string returned to the calling REXX program. It will contain one of the following values: 'GOOD' All processing went normally (the parameters received were syntactically correct and AUEUSRGA successfully delivered to AUEPITCH the request to build and ship the generic alert to AUECATCH). 'BAD: message text' There was an error. Error messages are also written to the LMU/2 messages log, which may give more detailed information about the failure cause) Note: If the return code received is 0 (the request had correct syntax and was successfully delivered from AUEUSRGA to AUEPITCH) but the generic alert seems not to flow from AUEPITCH to AUECATCH, you will need to check the LMU/2 message log to determine if AUEPITCH encountered errors in its processing. Error_Number An unsigned short integer that identifies the type of generic alert you want built. See the error number mappings table in topic Error_Number Mappings for valid values and the generic alert that will be built. Appl_ID A string with the name of the user program that is requesting that the alert be built and shipped. This string has a maximum length of 8 bytes and will be displayed at the NetView console (Hardware Monitor Alerts Dynamic and Alert Detail panels). In the event that you want to drive an automation routine from this alert via the fault manager, be careful to make the first 7 bytes unique, as only 7 characters are allowed in the alerts table entry for Software Product Name (see User-Defined Table for details on the alerts table). Message A string of free-format text that you want displayed at the NetView console (Alert Details panel). This text may also be passed to an automation routine by specification of the proper SV_Parm in the alerts table file (see User-Defined Table for details on the alerts table). Note: Because the LMU/2 command transport initiates the automation routine using the standard OS/2 command line interface, any special symbols in the message string may be misinterpreted by the OS/2 command shell (< and > become redirection, | becomes a pipe, and so forth). To use the symbols as literal symbols, place a double quote in the alerts table Command field as directed in topic Command. The message has a maximum length of 44 characters. Event_CPU Optional . A string with the name of the resource experiencing the fault condition. If the Event_CPU string is not present, the alert is built using the name of the computer executing the REXX program (COMPUTERNAME if IBM LAN Requester, internetwork address if Novell NetWare Requester) as the resource experiencing the alert condition. If present and representing an IBM LAN Requester, the string may be up to 8 bytes in length and will cause the Resource Hierarchy to be built with an additional (third) field, indicating that the machine raising the alert is different from the machine on which the condition exists. If present and representing a Novell NetWare Requester, the string may be up to 22 bytes in length and will cause the Resource Hierarchy List to contain the name NOVELL and will cause the Single MAC Address to contain the node address from the Novell internetwork address. Continue with Alert Generation and Routing ΓòÉΓòÉΓòÉ 24.1.4. AUEREX01.CMD ΓòÉΓòÉΓòÉ AUEREX01.CMD is a sample REXX program to generate a generic alert. The program uses the RxFuncQuery statement to determine if the external function has been defined and, if not, issues the RxFuncAdd command to register it. It then makes a call to AUEREXGA to create an alert for Error_Code 21. This alert will be displayed at the NetView operator console as a Permanent Software error on the workstation running the REXX program. Its Probable Cause will be "Undetermined", the Failure Cause will be as indicated in the message text provided to AUEREXGA, and the Recommended Action will be to "Perform Problem Determination Procedures". The Resource Hierarchy will display two components: the Application Name passed to AUEREXGA, and the COMPUTERNAME of the workstation. The REXX program will display the Return String from the call to AUEREXGA. Continue with Alert Generation and Routing ΓòÉΓòÉΓòÉ 24.1.5. AUEDOSAL.COM ΓòÉΓòÉΓòÉ AUEDOSAL is a simple program to generate a generic alert on a DOS station. It is run from a batch file (or can be typed from the DOS command line), and generates an alert based on the error number specified or passed to it. The format of the AUEDOSAL statement is: AUEDOSAL Error_Number Appl_ID Message When AUEDOSAL is initiated from the command line, the parameters must be specified explicitly. For example: AUEDOSAL 21 MYAPPL Sample message line. Parameter Meaning Error_Number An unsigned short integer that identifies the type of generic alert you want built. See the error number mappings table in topic Error_Number Mappings for valid values and the generic alert that will be built. Appl_ID A string with the name of the user program that is requesting that the alert be built and shipped. This string has a maximum length of 8 bytes and will be displayed at the NetView console (Hardware Monitor Alerts Dynamic and Alert Detail panels). In the event that you want to drive an automation routine from this alert via the fault manager, be careful to make the first 7 bytes unique, as only 7 characters are allowed in the alerts table entry for Software Product Name (see User-Defined Table for details on the alerts table). Message A string of free-format text that you want displayed at the NetView console (Alert Details panel). This text may also be passed to an automation routine by specification of the proper SV_Parm in the alerts table file (see User-Defined Table for details on the alerts table). Note: Because the LMU/2 command transport initiates the automation routine using the standard OS/2 command line interface, any special symbols in the message string may be misinterpreted by the OS/2 command shell (< and > become redirection, | becomes a pipe, and so forth). To use the symbols as literal symbols, place a double quote in the alerts table Command field as directed in topic Command. The message has a maximum length of 44 characters. Continue with Alert Generation and Routing ΓòÉΓòÉΓòÉ 24.1.6. Error_Number Mappings ΓòÉΓòÉΓòÉ The alert type and alert description are based on the Error_Number you pass AUEUSRGA or AUEDOSAL. The primary difference between the alerts created is the Alert Type and Alert Description, which affects the text for Probable Cause, Recommended Action, and Detailed data that will be displayed at the NetView console. The mapping is as follows: ERROR CODE CODE NUMBER ALERT DESCRIPTION POINT ALERT TYPE POINT 21 Software 2100 Permanent Loss 01 22 Software 2100 Temporary Loss 02 23 Software 2100 Impending Loss 11 41 Performance 4000 Permanent Loss 01 42 Performance 4000 Temporary Loss 02 43 Performance 4000 Impending Loss 11 51 Congestion 5000 Permanent Loss 01 52 Congestion 5000 Temporary Loss 02 53 Congestion 5000 Impending Loss 11 91 Intervention Reqd 9000 Permanent Loss 01 102 Problem Resolved A000 Temporary Loss 02 Continue to AUEUSRGA Generic Alert Table ΓòÉΓòÉΓòÉ 24.1.7. AUEUSRGA Generic Alert Table ΓòÉΓòÉΓòÉ Error_Number Alert Content 21 Type : PERMANENT Description : SOFTWARE PROGRAM ERROR Probable Cause : UNDETERMINED Recommended Action : PERFORM PROBLEM DETERMINATION PROCEDURES Failure Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 01 2100 Source_CPUNAME Table Entry (SV-PARM ): 96 22 Type : TEMPORARY Description : SOFTWARE PROGRAM ERROR Probable Cause : SOFTWARE PROGRAM Recommended Action : NO ACTION NECESSARY User Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 02 2100 Source_CPUNAME Table Entry (SV-PARM ): 94 23 Type : IMPENDING Description : SOFTWARE PROGRAM ERROR Probable Cause : SOFTWARE PROGRAM Recommended Action : CONTACT LAN ADMINISTRATOR RESPONSIBLE FOR THIS LAN User Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 11 2100 Source_CPUNAME Table Entry (SV-PARM ): 94 41 Type : PERMANENT Description : PERFORMANCE DEGRADED Probable Cause : UNDETERMINED Recommended Action : PERFORM PROBLEM DETERMINATION PROCEDURES Failure Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 01 4000 Source_CPUNAME Table Entry (SV-PARM ): 96 42 Type : TEMPORARY Description : PERFORMANCE DEGRADED Probable Cause : SOFTWARE PROGRAM Recommended Action : NO ACTION NECESSARY User Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 02 4000 Source_CPUNAME Table Entry (SV-PARM ): 94 43 Type : IMPENDING Description : PERFORMANCE DEGRADED Probable Cause : SOFTWARE PROGRAM Recommended Action : CONTACT LAN ADMINISTRATOR RESPONSIBLE FOR THIS LAN User Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 11 4000 Source_CPUNAME Table Entry (SV-PARM ): 94 51 Type : PERMANENT Description : CONGESTION Probable Cause : UNDETERMINED Recommended Action : PERFORM PROBLEM DETERMINATION PROCEDURES Failure Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 01 5000 Source_CPUNAME Table Entry (SV-PARM ): 96 52 Type : TEMPORARY Description : CONGESTION Probable Cause : SOFTWARE PROGRAM Recommended Action : NO ACTION NECESSARY User Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 02 5000 Source_CPUNAME Table Entry (SV-PARM ): 94 53 Type : IMPENDING Description : CONGESTION Probable Cause : SOFTWARE PROGRAM Recommended Action : CONTACT LAN ADMINISTRATOR RESPONSIBLE FOR THIS LAN User Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 11 5000 Source_CPUNAME Table Entry (SV-PARM ): 94 91 Type : PERMANENT Description : INTERVENTION REQUIRED Probable Cause : UNDETERMINED Recommended Action : PERFORM PROBLEM DETERMINATION PROCEDURES Failure Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 01 9000 Source_CPUNAME Table Entry (SV-PARM ): 96 102 Type : TEMPORARY Description : PROBLEM RESOLVED Probable Cause : SOFTWARE PROGRAM Recommended Action : NO ACTION NECESSARY User Cause : MESSAGE : (message text passed by application) Table Entry (Key Data): Appl_ID 02 A000 Source_CPUNAME Table Entry (SV-PARM ): 94 Note: The text displayed at the network management focal point may be slightly different than that indicated above, because different products (IBM NetView, IBM LAN Manager 2.0, and IBM LAN Network Manager 1.0, for example) implement the SNA Management Services Architecture differently on occasion. ΓòÉΓòÉΓòÉ 25. Sample Logs ΓòÉΓòÉΓòÉ This appendix contains sample watch logs and a sample change log. Choose any of the following to view: o Sample PERFCAP Watch Log o Sample PERFWACH Watch Log o Sample OSRWATCH Watch Log o Sample Change Log ΓòÉΓòÉΓòÉ 25.1. Sample PERFCAP Watch Log ΓòÉΓòÉΓòÉ This watch log was produced during the execution of PERFCAP and illustrates the dependence on the System Performance Monitor/2 (SPM/2) programs. A watch log is included here because it reveals the manner in which PERFCAP operates. It is also useful in discussing the data produced from SPMDCF. The command that produced this log was: perfcap /i60 /wperfcap.out 0 Open pipe \PIPE\SYSTEM.SPM ΓöÇΓöÉ 0 /THESEUS Γöé 0 START Γöé System Pipe return value 0000, 0000 Γöé 0 /COMMENT Γöé 0 PERFCAP on 06-05-1991 at 10:35:45 for 0060 Γöé Note 1 System Pipe return value 0000, 0000 Γöé 0 /START * LOGICALDISK Γöé 0 ##### Γöé System Pipe return value 0000, 0000 ΓöÇΓöÿ 0 Open pipe \PIPE\TRACE.SPM ΓöÇΓöÉ Note 2 Trace Pipe read 41 times for a total of 32957 bytes. ΓöÇΓöÿ 0 Close pipe \PIPE\TRACE.SPM ΓöÇΓöÉ 0 /STOP * LOGICALDISK Γöé 0 ##### Γöé Note 3 System Pipe return value 0000, 0000 Γöé 0 Close pipe \PIPE\SYSTEM.SPM ΓöÇΓöÿ Records 01 34 02 1678 10 13 11 0 21 60 22 42 23 0 31 0 32 7 ΓöÇΓöÉ Note 4 Records 12 1 13 5 14 0 18 0 24 6 25 79 26 0 27 437 28 0 29 5 ΓöÇΓöÿ RAM Install Avail InWS OutWS Free ΓöÇΓöÉ 0010354688 0007381216 0004530144 0005559744 0000264800 Γöé Note 5 0 Call transport for RAM data ΓöÇΓöÿ Disk Read Sect Time ; Write Sect Time ; WritV Sect Time ΓöÇΓöÉ 0080 60 274 1.9206 42 180 1.7355 0 0 0.0000 Γöé Note 6 Total time listed is 3.6561 seconds. Γöé 0 Call transport for disk data ΓöÇΓöÿ SwapIN Cnt SegL Xeq Time ; SwapOUT Cnt SegL Xeq Time ΓöÇΓöÉ 0 0 0.0000 7 71968 0.8514 Γöé Note 7 Total time listed is 0.8514 seconds. Γöé 0 Call transport for swap data ΓöÇΓöÿ LIO PID Name Hndl Act RCnt WCnt Filename ΓöÇΓöÉ 0032 SPMDCF 0009 Rd 1208 3 Γöé 0035 THESEUS 0001 Wr 0 1208 Γöé 0035 THESEUS 0003 Wr 0 1208 Γöé 0032 SPMDCF 0001 Wr 0 18 Γöé 0034 SPMLOG 0003 Wr 0 1355 Γöé 0032 SPMDCF 0004 Wr 0 31957 Γöé Note 8 0039 PERFCAP 0005 Rd 31957 0 Γöé 001F LC 0003 Cls 0 0 C:\IBMLAN\LOGS\MESSAGES.LOG Γöé 003C FVP 0003 Cls 2919 0 C:\TOOLS\FVP.CNF Γöé 003C FVP 0001 Wr 0 54 Γöé 003C FVP 0000 Opn 0 0 F:\XQ4\PERFCAP.OUT Γöé 0 Call transport for logical I/O data ΓöÇΓöÿ PID Name Disps Xeq Time Int Time Pct ΓöÇΓöÉ 0032 SPMDCF 113 0.8143 0.0196 1.35 Γöé 0036 IDLECPU 40 3.6935 0.1144 6.11 Γöé 0035 THESEUS 42 0.8278 0.0236 1.37 Γöé 0034 SPMLOG 31 0.0830 0.0016 0.14 Γöé 0005 PMSHELL 447 1.6911 0.0317 2.80 Γöé 0003 Swapper 21 0.0406 0.0015 0.07 Γöé 0004 ACSTRSYS 4 0.0043 0.0000 0.01 Γöé 0007 PMSPOOL 3 0.0079 0.0000 0.01 Γöé 0008 PMEXEC 14 0.0203 0.0015 0.03 Γöé Note 9 000D COLLAGE 687 47.7015 1.4939 78.91 Γöé 0011 PMDIARY 123 0.5191 0.0107 0.86 Γöé 0012 DIRUTILY 18 0.6333 0.0274 1.05 Γöé 0017 WKSTA 6 0.0294 0.0005 0.05 Γöé 0019 WKSTAHLP 3 0.0088 0.0010 0.01 Γöé 001F LC 9 0.0560 0.0000 0.09 Γöé 0039 PERFCAP 19 0.5247 0.0188 0.87 Γöé 003B 69 2.4254 0.0724 4.01 Γöé 003C FVP 28 1.3350 0.0362 2.21 Γöé Total time listed is 60.4536 seconds. Γöé 0 Call transport for process data ΓöÇΓöÿ LMU5000I PERFCAP data from 10:35:45 for 0060 delivered. Highest rc=0 ΓöÇΓöÉ Γöé Note 10 About to sleep for 0 seconds ΓöÇΓöÿ Notes: 1. This section shows the system pipe being opened (SPMDCF was already present in the system because the open succeeded on the first attempt). It shows the commands sent over the system pipe to start data collection, and the return codes received in response to those commands. 2. This section shows the trace pipe being opened, and, at this point, the trace pipe is read for the entire collection interval. At the end of the collection interval, a message indicates how many times the trace pipe was read and how many bytes of trace data were received during the collection interval. In this watch log, 32,957 bytes were received in 41 reads. 3. At the completion of the capture interval, the trace pipe is closed, SPMDCF is quiesced (the /STOP command), and the system pipe is closed. 4. This section shows a summary of all of record types received during the collection interval. The record type is listed first, followed by the number of records received of that type. Refer to System Performance Monitor/2 Reference Manual for a description of the record types and their layout. 5. This section begins the summary information for the data to be sent to the managing system database. The data shown here is the last RAM record received during the interval and carries the total memory installed, the amount of available memory, the memory considered to be in and out of the working set, and the amount of memory free for new application use. At the end of this section is a call to the LAN Management Utilities/2 transport and its return code. This is the call that places the data on the LAN Management Utilities/2 transport for delivery to the managing system database. The 0 return code indicates that the data was successfully placed on the transport, not that it arrived or was correctly handled at the managing system database. This call is made (and shown) for each set of data that was collected over the interval. 6. This section shows the physical disk aggregate data that is supplied to the managing system database. The information includes the physical disk ID and activity data for reads, writes, and write verifies. For each of these, the count, number of sectors, and execution time for the activity is given. Since execution time is provided, the summary ends with a total of all time that is accounted for in the previous records. This total time is a part of the header information sent to the database. Although it may not be interesting with respect to the physical disk data, it can be used to calculate activity percentages as part of the whole. 7. This section shows the swap aggregate data that is supplied to the managing system database. The information includes the disk activity for swaps in and out. For each of these, the count, total segment length, and execution time for the activity are given. Since execution time is provided, the summary ends with a total of all time that is accounted for in the previous records. This total time is a part of the header information sent to the database and can be used to calculate activity percentages as part of the whole. 8. This section summarizes the logical disk I/O record aggregates as created during the collection interval. The information includes process ID and file handle of the logical file, the last action performed, the count of bytes read and written, and (if available) the file spec of the logical file. Possible values for the last action are Opn (open), Cls (close), Rd (read), RdA (read asynchronous), Wr (write), and WrA (write asynchronous). Notice that SPMDCF (PID 0032, hndl 0004) wrote 31957 bytes and PERFCAP (PID 0039, hndl 0005) read 31957 bytes during the collection period. This corresponds to the trace pipe data that was transferred between the processes. The file that appears in the summary on the F: drive is owned by another server and illustrates that remote disk files are supported as well as local file activity. 9. This section shows the process aggregate data that is supplied to the managing system database. The information includes the process ID, process name, number of dispatches, execution time and interrupt time for the process, and the percentage of the execution time to the total time accounted for by all the process records (for example, the total 60.4536 seconds listed at the bottom of the section). This percentage is not part of the data sent to the database, but the total time listed value is part of the data header (as discussed in previous notes). Also, the watch log summary does not include those processes which had zero dispatches. The processes with no activity are part of the data sent to the managing system database, but they are not listed in the watch log. Note that the total time accounted for is 60.4536 seconds although the capture interval was 60 seconds. The time accounted for by all received records never exactly matches the requested interval (sometimes a little more, sometimes a little less). This is why both the interval time and the actual time are sent with the header information for those aggregates which involve time. 10. This section shows a copy of the message that is written to the LAN Management Utilities/2 log file after all data has been sent over the transport. This message indicates that all data for a capture interval has been sent to the managing system database, and shows the highest return code received for calls to the transport mechanism. The sleep message in this section shows that PERFCAP determined that it did not need to remove itself for a period of time. If PERFCAP were running for a long duration (/d value), this message would show how many seconds PERFCAP would sleep before the frequency period expired and the entire loop would be repeated. 11. If /x had been specified, PERFCAP would have completed by reopening the system pipe and sending a termination sequence to SPMDCF (STOP to THESEUS and /EXIT to SPMDCF). After the final system pipe close, PERFCAP terminates. ΓòÉΓòÉΓòÉ 25.2. Sample PERFWACH Watch Log ΓòÉΓòÉΓòÉ This watch log was produced by PERFWACH, and shows tracking information. 3 Open pipe \PIPE\SYSTEM.SPM ΓöÇΓöÉ 3 Open pipe \PIPE\SYSTEM.SPM Γöé 3 Open pipe \PIPE\SYSTEM.SPM Γöé 0 DosStartSession for SPMDCF Γöé 3 Open pipe \PIPE\SYSTEM.SPM Γöé 231 Open pipe \PIPE\SYSTEM.SPM Γöé 0 Open pipe \PIPE\SYSTEM.SPM Γöé 0 /THESEUS Γöé Note 1 0 START Γöé System Pipe return value 0000, 0000 Γöé 0 /COMMENT Γöé 0 PERFWACH on 06-11-1991 at 09:43:40 for 0060 Γöé System Pipe return value 0000, 0000 Γöé 0 /START * Γöé 0 ##### Γöé System Pipe return value 0000, 0000 Γöé 0 Open pipe \PIPE\TRACE.SPM Γöé Trace Pipe read 44 times for a total of 35711 bytes. Γöé 0 Close pipe \PIPE\TRACE.SPM Γöé 0 /STOP * Γöé 0 ##### Γöé System Pipe return value 0000, 0000 Γöé 0 Close pipe \PIPE\SYSTEM.SPM ΓöÇΓöÿ Records 01 36 02 2089 10 12 11 0 21 132 22 21 23 0 31 0 32 6 ΓöÇΓöÉ Note 2 Records 12 1 13 5 14 0 18 0 24 0 25 0 26 0 27 0 28 0 29 0 ΓöÇΓöÿ Threshold values: PROC:10 DISK:01 SWAP:10 FREE:10 ΓöÇΓöÇ Note 3 LMU5104I FREE memory < 10% 00222816,07404256 ΓöÇΓöÉ 8 Error creating FREE generic alert Γöé LMU5102I DISK active > 01% 005.1695,0060 Γöé Note 4 8 Error creating DISK generic alert Γöé LMU5101I PROC active > 10% COLLAGE at 61.8% Γöé 8 Error creating PROC generic alert ΓöÇΓöÿ About to sleep for 0 seconds ΓöÇΓöÇ Note 5 Notes: 1. The design and execution of PERFWACH is very much like PERFCAP. PERFWACH begins by attempting to open the SPM system pipe. In this particular watch log, SPMDCF is not active in the workstation and the complete sequence for starting SPMDCF and initiating data transfer is shown. As with PERFCAP, the trace pipe is opened and read for the entire interval. A message is generated to show the number of reads and the total number of bytes read. Once the interval expires, the system pipe is closed and the aggregated data is evaluated for thresholds. 2. The records received per trace record type are summarized in the watch log. 3. The thresholds in effect for this execution are displayed for tracking purposes. As you can see, the threshold values are quite low in order to illustrate the alert generation. 4. Three alerts were generated. The user data portion of the alert is echoed in the watch log. In this case, AUEPITCH was not executing in the workstation, so the generated alerts could not be delivered to the fault manager. If a non-zero return code is received from the alert generation interface (AUEUSRGA), an error message is placed in the watch log (as shown). If a zero return code is received from AUEUSRGA, no message is placed in the watch log. 5. The loop is completed by determining the amount of time PERFWACH should sleep before the next frequency interval. In this case, PERFWACH was run for one time only. ΓòÉΓòÉΓòÉ 25.3. Sample OSRWATCH Watch Log ΓòÉΓòÉΓòÉ This watch log was produced by OSRWATCH, and shows the adapter activity during the time OSRWATCH was executing. This watch log was created with the following command: osrwatch /f3 /d180 /w The threshold values that were used came from the .INI file of the local workstation. Note that they are set to values that will demonstrate alert generation, and are not realistic threshold settings. 06/24/1991 08:00:10 OSRWATCH begins for server: \\EXMPSERV 06/24/1991 08:00:10 Logon set return code 0. Process 13 out of 13 users. 06/24/1991 08:00:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 06/24/1991 08:00:10 New user to \\EXMPSERV: XMPLIB1, LIBSERV (03) XMPLIB1 XXXX(29)XX 06/24/1991 08:00:10 NCB count at XMPLIB1, LIBSERV is below 50 percent 19 of 41 are currently free 06/24/1991 08:00:10 XMT error(s) 1850 at XMPLIB1, LIBSERV 06/24/1991 08:00:10 RCV error(s) 4 at XMPLIB1, LIBSERV 06/24/1991 08:00:10 Aborted transmission(s) 543 at XMPLIB1, LIBSERV 06/24/1991 08:00:10 T1 timer expiration(s) 1561 at XMPLIB1, LIBSERV 06/24/1991 08:00:10 New user to \\EXMPSERV: EXMPSERV, EXMPADM (03) EXMPSERV XXXX(41)XX 06/24/1991 08:00:10 NCB count at EXMPSERV, EXMPADM is below 50 percent 12 of 41 are currently free 06/24/1991 08:00:10 XMT error(s) 61 at EXMPSERV, EXMPADM 06/24/1991 08:00:10 RCV error(s) 736 at EXMPSERV, EXMPADM 06/24/1991 08:00:10 Aborted transmission(s) 445 at EXMPSERV, EXMPADM 06/24/1991 08:00:10 T1 timer expiration(s) 382 at EXMPSERV, EXMPADM 06/24/1991 08:00:10 New user to \\EXMPSERV: CATES, CATES (03) CATES XXXXX 06/24/1991 08:00:10 New user to \\EXMPSERV: SIGRIST, SIGRIST (03) SIGRIST X 06/24/1991 08:00:10 New user to \\EXMPSERV: DELLIS, DELLIS (03) DELLIS X 06/24/1991 08:00:10 New user to \\EXMPSERV: MXMPUS1, DMILLER (03) MXMPUS1 XXX 06/24/1991 08:00:10 New user to \\EXMPSERV: CHICK, CHICK (03) CHICK X 06/24/1991 08:00:10 New user to \\EXMPSERV: LOTTER, LOTTER (03) LOTTER X 06/24/1991 08:00:10 New user to \\EXMPSERV: MXMPUS2, MPRGMR01 (03) MXMPUS2 X 06/24/1991 08:00:10 New user to \\EXMPSERV: JOESP70, JOE (02) 06/24/1991 08:00:10 New user to \\EXMPSERV: EXMPTCF, FRICK (03) 06/24/1991 08:00:10 New user to \\EXMPSERV: JPLOEWEN, JPLOEWEN (03) JPLOEWEN X 06/24/1991 08:00:10 New user to \\EXMPSERV: MXMPUS4, SCHMIDT (03) 06/24/1991 08:00:10 User logons 13 at \\EXMPSERV exceed 10. 06/24/1991 08:00:10 Total packet activity: receives 42457, transmits 42142 06/24/1991 08:02:10 Logon set return code 0. Process 13 out of 13 users. 06/24/1991 08:02:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 EXMPSERV X MXMPUS4 X 06/24/1991 08:02:10 Total packet activity: receives 1187, transmits 1181 06/24/1991 08:04:10 Logon set return code 0. Process 13 out of 13 users. 06/24/1991 08:04:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 EXMPSERV X SIGRIST X 06/24/1991 08:04:10 Total packet activity: receives 1016, transmits 1020 ---------- portion of watch log deleted ------------------------------------------------------- 06/24/1991 08:14:10 Logon set return code 0. Process 15 out of 15 users. 06/24/1991 08:14:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 06/24/1991 08:14:10 New user to \\EXMPSERV: JOELH, JOELH (03) 06/24/1991 08:14:10 New user to \\EXMPSERV: KRUM, KRUM (03) 06/24/1991 08:14:10 User logons 15 at \\EXMPSERV exceed 10. 06/24/1991 08:14:10 Total packet activity: receives 612, transmits 421 06/24/1991 08:16:10 Logon set return code 0. Process 16 out of 16 users. 06/24/1991 08:16:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 06/24/1991 08:16:10 New user to \\EXMPSERV: MXMPUS5, BONACK (03) 06/24/1991 08:16:10 User logons 16 at \\EXMPSERV exceed 10. 06/24/1991 08:16:10 Total packet activity: receives 727, transmits 645 ---------- portion of watch log deleted ------------------------------------------------------- 06/24/1991 08:24:10 Logon set return code 0. Process 17 out of 17 users. 06/24/1991 08:24:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 EXMPSERV XXXX JPLOEWEN XX JOELH XX 06/24/1991 08:24:10 Total packet activity: receives 4614, transmits 4612 06/24/1991 08:26:10 Logon set return code 0. Process 17 out of 17 users. 06/24/1991 08:26:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 XMPLIB1 X EXMPSERV X MXMPUS2 X JPLOEWEN X 06/24/1991 08:26:10 Total packet activity: receives 1509, transmits 1491 06/24/1991 08:28:10 Logon set return code 0. Process 18 out of 18 users. 06/24/1991 08:28:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 06/24/1991 08:28:10 Session availability at EXMPSERV, EXMPADM is below 50 percent. 21 of 41 sessions are currently in use 06/24/1991 08:28:10 New user to \\EXMPSERV: MXMPUS3, CONNIE (03) 06/24/1991 08:28:10 NCB.STATUS return code for DELLIS is 5 06/24/1991 08:28:10 User logons 18 at \\EXMPSERV exceed 10. 06/24/1991 08:28:10 Total packet activity: receives 818, transmits 722 06/24/1991 08:30:10 Logon set return code 0. Process 18 out of 18 users. 06/24/1991 08:30:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 EXMPSERV X JPLOEWEN X 06/24/1991 08:30:10 Total packet activity: receives 1701, transmits 1688 06/24/1991 08:32:10 Logon set return code 0. Process 18 out of 18 users. 06/24/1991 08:32:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 XMPLIB1 X EXMPSERV X MXMPUS1 X JPLOEWEN X 06/24/1991 08:32:10 Total packet activity: receives 2364, transmits 2366 06/24/1991 08:34:10 Logon set return code 0. Process 18 out of 18 users. 06/24/1991 08:34:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 06/24/1991 08:34:10 Total packet activity: receives 329, transmits 327 06/24/1991 08:36:10 Logon set return code 0. Process 18 out of 18 users. 06/24/1991 08:36:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 EXMPSERV XX 06/24/1991 08:36:10 NCB.STATUS return code for DELLIS is 0 JPLOEWEN XX JOELH X 06/24/1991 08:36:10 Total packet activity: receives 2454, transmits 2451 06/24/1991 08:38:10 Logon set return code 0. Process 18 out of 18 users. 06/24/1991 08:38:10 Thresholds - NCBS:050 NSES:050 NERR:001 NABT:001 NDTO:001 NLGN:010 NBFX:001 06/24/1991 08:38:10 Total packet activity: receives 147, transmits 148 Notes: 1. 08:00 OSRWATCH is started and generates an initiation message stating the server that is the source of the logon set. OSRWATCH determines the logon set and states the number of logons that were detected and the number of adapters that will be monitored. Threshold exceptions are determined by comparing the data from the current collection with that of the previous collection. Since OSRWATCH is initializing, all comparisons are being made against zero values. This causes the watch log to report adapter data since the adapter was last reset. No alerts are generated from an initial set of adapter data (the New user indication), but this information is supplied in the watch log. On each pass, a message is placed in the watch log indicating the thresholds in use at the time. The threshold values shown have been set low in order to generate information for the watch log. The first set of adapter information is returned for requester XMPLIB1. Where change conditions are detected (values that are non-zero in the first pass), messages are placed in the watch log for XMPLIB1: a. LIBSERV is logged on to requester XMPLIB1. The NETBIOS level is 03; therefore, this is an OS/2 client. Also, the packet activity since the last pass (again compared to 0 initially) is indicated by the XXX's (one X for each 1000 packets sent and received). This adapter shows approximately 29,000 packets of activity since the adapter was last reset. b. The NCB count is below the specified threshold (50%). The values used for comparison are also shown (19 of 41). c. The adapter has had 1850 transmit errors and 4 receive errors since it was last reset. d. The adapter has had 543 aborted transmissions since it was last reset. e. The adapter has had 1561 T1 timer expirations since it was last reset. The other adapter data is listed as it is collected for other members of the logon set. At the end of the collection period, the total number of active users is compared to the threshold for user logons. This value was exceeded and a message is placed in the watch log. Also at the end of the collection period, the total number of transmitted and received packets (across all of the data collected) is listed. 2. 08:02 OSRWATCH collects a logon set. The set has not changed (no new user entries appear), and data collection occurs for all members of the set. No change conditions appear in the data. Requesters EXMPSERV and MXMPUS4 each had about 1000 packets of send and transmit traffic during the period. The other requesters had less than 1000 packets worth of activity. 3. 08:14 Two new users have logged on since the last collection interval and are reflected in New user entries. The number of active users has changed and still exceeds the threshold of 10, so an alert is generated for this condition. Other than this, nothing interesting has happened. 4. 08:28 The NSES threshold at EXMPSERV is exceeded. The values used for comparison (21 of 41) are indicated in the watch log. Also of interest is that requester DELLIS did not respond to the query made to the adapter (the user most likely powered off the workstation). This status for DELLIS is saved with the data for that requester. The adapter will continue to be queried at each pass, but nothing will be reported for that adapter unless the NCB.STATUS return code changes from 5. 5. 08:36 The adapter status return code for DELLIS changed and appears to be back on the ring. The last set of adapter data remains with the entry for this requester and is the basis for the next comparison. ΓòÉΓòÉΓòÉ 25.4. Sample Change Log ΓòÉΓòÉΓòÉ The change log is produced by the LMUSRV program. See the change log discussion in topic Change Log. The change log contains three columns: item name, current data, and previous data. Note: User programs accessing a change log should not rely on column positions but should use the embedded arrows to identify the beginning of fields. ITEM NAME: CURRENT DATA: PREVIOUS DATA: Computer -> LSERVER Report Date -> 1992-04-20 -> 1992-04-20 Report Time -> 09.21.39 -> 07.56.02 File C:\STARTUP.CMD Last Wr -> 1992-04-20-09.02.38.00 -> 1992-04-17-21.29.52.00 itten -+ 0000 -+ 0000 File C:\STARTUP.CMD Size -> 118 -> 191 File C:\LMU.LOG Last Writte -> 1992-04-20-09.21.08.00 -> 1992-04-20-07.38.36.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 29703 -> 29272 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 11.17.27 -> 07.57.58 File C:\LMU.LOG Last Writte -> 1991-04-20-11.15.28.00 -> 1991-04-20-07.18.32.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 7675 -> 6884 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 11.17.27 -> 07.58.00 Drive X: Type -> LAN -> - Network Name -> \\LSERVER\LMU2 -> - Drive Y: Type -> LAN -> - Network Name -> \\LSERVER\SPM2 -> - File C:\LMU.LOG Last Writte -> 1991-04-20-11.16.10.00 -> 1991-04-20-07.53.50.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 17653 -> 16014 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 13.36.20 -> 11.17.27 File C:\LMU.LOG Last Writte -> 1991-04-20-13.35.28.00 -> 1991-04-20-11.16.10.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 20522 -> 17653 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 13.37.10 -> 11.17.27 File C:\LMU.LOG Last Writte -> 1991-04-20-13.36.48.00 -> 1991-04-20-11.15.28.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 9333 -> 7675 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 13.38.26 -> 13.37.10 File C:\LMU.LOG Last Writte -> 1991-04-20-13.37.40.00 -> 1991-04-20-13.36.48.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 9407 -> 9333 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 13.38.33 -> 13.36.20 File C:\LMU.LOG Last Writte -> 1991-04-20-13.38.34.00 -> 1991-04-20-13.35.28.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 20931 -> 20522 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 18.24.29 -> 13.38.26 File C:\LMU.LOG Last Writte -> 1991-04-20-18.09.20.00 -> 1991-04-20-13.37.40.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 9966 -> 9407 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 18.25.13 -> 13.38.33 File C:\LMU.LOG Last Writte -> 1991-04-20-18.24.40.00 -> 1991-04-20-13.38.34.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 22260 -> 20931 ############################################################################### Computer -> LSERVER Report Date -> 1992-04-20 -> 1992-04-20 Report Time -> 18.25.28 -> 11.15.33 File C:\LMU.LOG Last Writte -> 1992-04-20-18.15.58.00 -> 1992-04-20-09.21.08.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 30393 -> 29703 SYSLEVEL.LMU C: V2.00 -> LM00100 -> LM00000 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 19.02.45 -> 18.24.29 File C:\LMU.LOG Last Writte -> 1991-04-20-19.02.02.00 -> 1991-04-20-18.09.20.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 10689 -> 9966 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-20 -> 1991-04-20 Report Time -> 19.15.45 -> 18.25.13 File C:\LMU.LOG Last Writte -> 1991-04-20-19.03.32.00 -> 1991-04-20-18.24.40.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 22758 -> 22260 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-21 -> 1991-04-20 Report Time -> 08.10.28 -> 19.15.46 File C:\LMU.LOG Last Writte -> 1991-04-21-08.03.36.00 -> 1991-04-20-19.02.02.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 1703 -> 10689 ############################################################################### Computer -> LSERVER Report Date -> 1992-04-21 -> 1992-04-20 Report Time -> 08.08.57 -> 19.13.54 File C:\LMU.LOG Last Writte -> 1992-04-21-08.04.00.00 -> 1992-04-20-18.15.58.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 1734 -> 30393 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-21 -> 1991-04-20 Report Time -> 08.10.30 -> 19.15.45 File C:\LMU.LOG Last Writte -> 1991-04-21-08.09.48.00 -> 1991-04-20-19.03.32.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 2600 -> 22758 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-21 -> 1991-04-21 Report Time -> 08.11.09 -> 08.10.30 File C:\LMU.LOG Last Writte -> 1991-04-21-08.10.50.00 -> 1991-04-21-08.09.48.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 2678 -> 2600 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-21 -> 1991-04-21 Report Time -> 08.34.08 -> 08.11.09 File C:\LMU.LOG Last Writte -> 1991-04-21-08.17.16.00 -> 1991-04-21-08.10.50.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 3325 -> 2678 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-21 -> 1991-04-21 Report Time -> 08.41.26 -> 08.34.07 File C:\LMU.LOG Last Writte -> 1991-04-21-08.41.00.00 -> 1991-04-21-08.03.36.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 2284 -> 1703 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-21 -> 1991-04-21 Report Time -> 10.15.18 -> 08.41.26 File C:\LMU.LOG Last Writte -> 1991-04-21-10.14.34.00 -> 1991-04-21-08.41.00.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 2939 -> 2284 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-21 -> 1991-04-21 Report Time -> 10.53.52 -> 10.15.18 File C:\LMU.LOG Last Writte -> 1991-04-21-10.49.58.00 -> 1991-04-21-10.14.34.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 3520 -> 2939 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-21 -> 1991-04-21 Report Time -> 12.54.06 -> 08.34.08 File C:\LMU.LOG Last Writte -> 1991-04-21-12.54.08.00 -> 1991-04-21-08.17.16.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 4815 -> 3325 ############################################################################### Computer -> LSERVER Report Date -> 1992-04-21 -> 1992-04-21 Report Time -> 12.52.52 -> 08.32.14 File C:\LMU.LOG Last Writte -> 1992-04-21-12.45.28.00 -> 1992-04-21-08.04.00.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 1796 -> 1734 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-21 -> 1991-04-21 Report Time -> 12.54.47 -> 10.53.52 File C:\LMU.LOG Last Writte -> 1991-04-21-12.48.36.00 -> 1991-04-21-10.49.58.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 4163 -> 3520 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-22 -> 1991-04-21 Report Time -> 11.28.18 -> 12.54.47 File C:\LMU.LOG Last Writte -> 1991-04-22-11.27.52.00 -> 1991-04-21-12.48.36.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 6915 -> 4163 ############################################################################### Computer -> LSERVER Report Date -> 1992-04-22 -> 1992-04-21 Report Time -> 11.26.27 -> 12.52.52 File C:\LMU.LOG Last Writte -> 1992-04-22-11.25.28.00 -> 1992-04-21-12.45.28.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 2616 -> 1796 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-22 -> 1991-04-21 Report Time -> 11.28.25 -> 12.54.06 File C:\STARTUP.CMD Last Wr -> 1991-04-22-10.54.38.00 -> 1991-04-17-15.25.48.00 itten -+ 0000 -+ 0000 File C:\STARTUP.CMD Size -> 427 -> 395 File C:\LMU.LOG Last Writte -> 1991-04-22-11.28.30.00 -> 1991-04-21-12.54.08.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 7145 -> 4815 ############################################################################### Computer -> LSERVER Report Date -> 1992-04-22 -> 1992-04-22 Report Time -> 14.08.07 -> 11.26.27 File C:\LMU.LOG Last Writte -> 1992-04-22-14.03.56.00 -> 1992-04-22-11.25.28.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 2951 -> 2616 Continue on the next page of this chapter. ΓòÉΓòÉΓòÉ 25.5. Sample Change Log (continued) ΓòÉΓòÉΓòÉ ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-22 -> 1991-04-22 Report Time -> 14.55.24 -> 11.28.18 Managing System -> 00000000:10005A965325 -> 00000000:10005A261E29 File C:\LMU.LOG Last Writte -> 1991-04-22-14.54.30.00 -> 1991-04-22-11.27.52.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 8400 -> 6915 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-22 -> 1991-04-22 Report Time -> 15.01.07 -> 11.28.25 Serial Port(s) -> 1 -> 2 Total Memory -> 12160 -> 8064 Node Address -> 10005A965325 -> 10005A261E29 Universal Address -> 10005A965325 -> 10005A261E29 Slot 1 Adapter Id -> FDDF -> E001 Slot 2 Adapter Id -> E000 -> E016 File C:\LMU.LOG Last Writte -> 1991-04-22-14.55.30.00 -> 1991-04-22-11.28.30.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 8246 -> 7145 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-22 -> 1991-04-22 Report Time -> 16.02.28 -> 15.00.57 File C:\LMU.LOG Last Writte -> 1991-04-22-15.57.58.00 -> 1991-04-22-14.54.30.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 8959 -> 8400 ############################################################################### Computer -> LSERVER Report Date -> 1992-04-22 -> 1992-04-22 Report Time -> 16.01.00 -> 14.59.11 File C:\LMU.LOG Last Writte -> 1992-04-22-15.30.18.00 -> 1992-04-22-14.03.56.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 3286 -> 2951 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-22 -> 1991-04-22 Report Time -> 16.03.17 -> 15.01.07 Slot 1 Status -> ENABLED -> DISABLED Slot 1 POS Data -> FF0800FF -> FE0100FF File C:\LMU.LOG Last Writte -> 1991-04-22-16.03.10.00 -> 1991-04-22-14.55.30.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 9335 -> 8246 ############################################################################### Computer -> 10005A1C0005 Report Date -> 1991-04-23 -> 1991-04-22 Report Time -> 09.12.01 -> 16.02.28 File C:\LMU.LOG Last Writte -> 1991-04-23-09.10.26.00 -> 1991-04-22-15.57.58.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 9518 -> 8959 ############################################################################### Computer -> LMU2DEMO Report Date -> 1991-04-23 -> 1991-04-22 Report Time -> 09.13.02 -> 16.03.17 File C:\LMU.LOG Last Writte -> 1991-04-23-09.12.26.00 -> 1991-04-22-16.03.10.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 10213 -> 9335 ############################################################################### Computer -> LSERVER Report Date -> 1992-04-23 -> 1992-04-22 Report Time -> 09.11.25 -> 16.01.00 File C:\LMU.LOG Last Writte -> 1992-04-23-09.02.48.00 -> 1992-04-22-15.30.18.00 n -+ 0000 -+ 0000 File C:\LMU.LOG Size -> 3621 -> 3286 ############################################################################### ΓòÉΓòÉΓòÉ 26. IXFUTIL Utility ΓòÉΓòÉΓòÉ This appendix describes the IXFUTIL utility that is used to upload LMU database tables to an MVS host. Use this utility to exchange data between the IBM OS/2 EE 1.3 Database Manager (DBM) and Query Management Facility (QMF) on the host using Integration Exchange Format (IXF). There is a difference between the host QMF IXF format and the OS/2 IXF/PC format. This utility can be used to convert exported tables between these two formats and to upload the tables to an MVS host (to which an OS/2 Communications Manager 3270 emulator session on this workstation is logged on). IXFUTIL uses the Communications Manager SEND facility to transmit the converted tables to the MVS host. One of the advantages of using IXF for export and import is that the table definition and the data are embedded in a single file: that is, it is a self-contained file. ΓòÉΓòÉΓòÉ 26.1. Using IXFUTIL ΓòÉΓòÉΓòÉ The following sections describe how to use IXFUTIL. o Exporting Data from OS/2 to the Host o IXFUTIL Syntax o Conversion Problems o Limitations ΓòÉΓòÉΓòÉ 26.1.1. Exporting Data from OS/2 to the Host ΓòÉΓòÉΓòÉ To export an OS/2 DBM table to the host, perform the following steps: 1. Run the IXFUTIL procedure. This exports the table, converts it to host format and transfers it to the host using the IBM OS/2 Communications Manager SEND facility. 2. Switch to the host and invoke QMF. 3. Import the file using the QMF command IMPORT TABLE FROM yourfile. ΓòÉΓòÉΓòÉ 26.1.2. IXFUTIL Syntax ΓòÉΓòÉΓòÉ IXFUTIL prompts for any missing parameters, but can also be invoked with a full parameter string. See the syntax and discussion of parameters that follows. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöÇΓöÇIXFUTILΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇDBNAME dbnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö┤ΓöÇΓöÇ Γö£ΓöÇΓöÇTABLE table ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇSOURCEΓöÇΓöÇΓö¼ΓöÇΓöÇOS/2ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöñ Γöé ΓööΓöÇΓöÇHOSTΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇΓöÇFILE fileΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇXMITΓöÇΓöÇΓö¼ΓöÇΓöÇNOΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓööΓöÇΓöÇMVSΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇΓöÇLRECL lreclΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇMSG msgfileΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇCPID cpidΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γö£ΓöÇΓöÇHELPΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓööΓöÇΓöÇhelpΓöÇΓöÇΓöÿ Γöé Γö£ΓöÇΓöÇ?ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓööΓöÇΓöÇhelpΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇQUIETΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ The valid values are shown below. All keywords can be abbreviated to the first character, and unless the QUIET option is specified, the user is prompted for any required parameters that are missing. Dbname Name of the OS/2 database (required). Table Name of the OS/2 table (required). Source Source system. OS/2 or HOST (default is OS/2). File File name of exported data, OS/2 path name, or host file name. Xmit Transmit to or from host. MVS or NO. Default is NO. Lrecl Transmit-to-host record length when creating host files (Xmit must be MVS). Default is at least 81 and is obtained from the conversion program. Msg Name of message file in which IXFUTIL errors are logged. Default is IXFUTIL.MSG. Cpid Codepage ID for OS/2 file. Default is the current codepage. Help Request help for IXFUTIL syntax or use. For help on a parameter, enter HELP parametername (example: help lrecl). For general help on IXFUTIL, enter HELP with no parameters. ? Same as Help. Quiet Do not type message on the console or prompt for missing parameters. Note that options may be specified in OS/2 or TSO style: /option:value, option(value), or any combination thereof. Example: To convert and transfer an OS/2 DBM database table to an MVS host ready to be imported into a DB2 database table: IXFUTIL d(mydb) t(table_name) s(os) f(MVSQMF.IMPORT) x(MVS) ΓòÉΓòÉΓòÉ 26.1.3. Conversion Problems ΓòÉΓòÉΓòÉ When you perform an import to or export from an OS/2 database, detailed messages of the conversion are stored in the message file specified by the MSG option (default file is IXFUTIL.MSG). Examine this file in case of problems. ΓòÉΓòÉΓòÉ 26.1.4. Limitations ΓòÉΓòÉΓòÉ o If you create the host IXF file yourself, be sure to specify character mode for numeric data. o Fields of type LONG VARCHAR, GRAPHIC, VARGRAPHIC or LONG VARGRAPHIC are not supported. ΓòÉΓòÉΓòÉ 27. List of Abbreviations ΓòÉΓòÉΓòÉ ANSI American National Standards Institute. APPC Advanced Program-to-Program Communication. API Application program interface. ASCII American National Standard Code for Information Interchange. BIOS Basic Input/Output System. CNM Communication network management. CPU Central processing unit. CSD Corrective service diskette. C&SM Communications and system management. dBm Decibels based on 1 milliwatt. DBM Database Manager. DLC Data link control. DOS Disk Operating System. DTE Data terminal equipment. EBCDIC Extended binary-coded decimal interchange code. FDDI Fiber Distributed Data Interface. HDLC High-level data link control. IEEE Institute of Electrical and Electronics Engineers. I/O Input/output. IPL Initial program load. ISO International Organization for Standardization. IXF Integration exchange format. Kb Kilobit. KB Kilobyte. LAN Local area network. LMU/2 LAN Management Utilities/2. LLC Logical link control. LU Logical unit. MAC Medium access control. Mb Megabit. MB Megabyte. MHz Megahertz. MVS Multiple virtual storage. NCB Network Control Block. NETBIOS Network Basic Input/Output System. OSI Open Systems Interconnection. OS/2 Operating System/2. OS/2 EE Operating System/2 Extended Edition. PC Personal computer. PC DOS Personal Computer Disk Operating System. PC I/O channel Personal computer input/output channel. POS Programmable Option Select. PU Physical unit. QMF Query Management Facility. RAM Random access memory. SAA Systems Application Architecture. SAP Service access point. SDLC Synchronous data link control. SNA Systems Network Architecture. SPM/2 System Performance Monitor/2. SQL Structured Query Language. SSCP System services control point. UPS Uninterruptible power supply. VM Virtual machine. WAN Wide area network. ΓòÉΓòÉΓòÉ 28. Glossary ΓòÉΓòÉΓòÉ This Glossary defines local area network terms and abbreviations. It includes terms and definitions from the IBM Dictionary of Computing (Information Processing, Personal Computing, Telecommunications, Office Systems, IBM-Specific Terms), SC20-1699. o The symbol (A) identifies definitions from the American National Dictionary for Information Processing Systems, copyright 1982 by the Computer and Business Equipment Manufacturers Association (CBEMA). o The symbol (I) identifies definitions from the ISO Vocabulary-Information Processing and ISO Vocabulary-Office Machines, developed by the International Organization for Standardization, Technical Committee 97, Subcommittee 1. o The symbol (T) identifies definitions from draft international standards, draft proposals, and working papers in development by the International Organization for Standardization, Technical Committee 97, Subcommittee 1. ΓòÉΓòÉΓòÉ 28.1. Character A ΓòÉΓòÉΓòÉ active 1. Able to communicate on the network. A Token-Ring Network adapter is active if it is able to transmit and receive on the network. 2. Operational. 3. Pertaining to a node or device that is connected or is available for connection to another node or device. 4. Currently transmitting or receiving. adapter In a LAN, within a communicating device, a circuit card that, with its associated software and/or microcode, enables the device to communicate over the network. adapter address Twelve hexadecimal digits that identify a LAN adapter. address 1. In data communication, the IEEE-assigned unique code or the unique locally administered code assigned to each device or workstation connected to a network. 2. A character, group of characters, or a value that identifies a register, a particular part of storage, a data source, or a data sink. The value is represented by one or more characters. (T) 3. To refer to a device or an item of data by its address. (A) 4. The location in the storage of a computer where data is stored. 5. In word processing, the location, identified by the address code, of a specific section of the recording medium or storage. (T) alert 1. For IBM LAN management products, a notification indicating a possible security violation, a persistent error condition, or an interruption or potential interruption in the flow of data around the network. See also network management vector transport. 2. In SNA, a record sent to a system problem management focal point to communicate the existence of an alert condition. 3. In the NetView program, a high-priority event that warrants immediate attention. This data base record is generated for certain event types that are defined by user-constructed filters. alias An alternate name by which a named entity can be known on a network. See also name. American National Standard Code for Information Interchange (ASCII) The standard code, using a coded character set consisting of 7-bit coded characters (8 bits including parity check), used for information interchange among data processing systems, data communication systems, and associated equipment. The ASCII set consists of control characters and graphics characters. (A) application program 1. A program written for or by a user that applies to the user's work. Some application programs receive support and services from a special kind of application program called a network application program. 2. A program used to connect and communicate with stations in a network, enabling users to perform application-oriented activities. application program interface (API) The formally defined programming language interface that is between an IBM system control program or a licensed program and the user of the program. architecture A logical structure that encompasses operating principles including services, functions, and protocols. See computer architecture, network architecture, Systems Application Architecture (SAA), Systems Network Architecture (SNA). asynchronous 1. Pertaining to two or more processes that do not depend upon the occurrence of a specific event such as a common timing signal . (T) 2. In Fiber Distributed Data Interface (FDDI) rings, a type of data traffic that does not need bounded access delay to the medium and guaranteed throughput. attaching device Any device that is physically connected to a network and can communicate over the network. available memory In a personal computer, the number of bytes of memory that can be used after memory requirements for the operating system, device drivers, and other application programs have been satisfied. ΓòÉΓòÉΓòÉ 28.2. Character B ΓòÉΓòÉΓòÉ Basic Input/Output System (BIOS) In IBM personal computers with PC I/O channel architecture, microcode that controls basic hardware operations such as interactions with diskette drives, fixed disk drives, and the keyboard. binary 1. Pertaining to a system of numbers to the base two; the binary digits are 0 and 1. (A) 2. Pertaining to a selection, choice, or condition that has two possible different values or states. (I) (A) boot drive The disk drive from which the computer system was started. broadband local area network (LAN) A local area network (LAN) in which information is encoded, multiplexed, and transmitted through modulation of a carrier. (T) broadcast Simultaneous transmission of data to more than one destination. buffer 1. A portion of storage used to hold input or output data temporarily. 2. A routine or storage used to compensate for a difference in data rate or time of occurrence of events, when transferring data from one device to another. (A) bus 1. In a processor, a physical facility on which data is transferred to all destinations, but from which only addressed destinations may read in accordance with appropriate conventions. (I) 2. A network configuration in which nodes are interconnected through a bidirectional transmission medium. 3. One or more conductors used for transmitting signals or power. (A) byte 1. A string that consists of a number of bits, treated as a unit, and representing a character. (T) 2. A binary character operated upon as a unit and usually shorter than a computer word. (A) 3. A string that consists of a particular number of bits, usually 8, that is treated as a unit, and that represents a character. 4. A group of 8 adjacent binary digits that represent one extended binary-coded decimal interchange code (EBCDIC) character. 5. See n-bit byte. ΓòÉΓòÉΓòÉ 28.3. Character C ΓòÉΓòÉΓòÉ channel 1. A functional unit, controlled by a host computer, that handles the transfer of data between processor storage and local peripheral equipment. 2. A path along which signals can be sent. 3. The portion of a storage medium that is accessible to a given reading or writing station. 4. In broadband transmission, a designation of a frequency band 6 MHz wide. command 1. A request for performance of an operation or execution of a program. 2. A character string from a source external to a system that represents a request for system action. component 1. Any part of a network other than an attaching device, such as an IBM 8228 Multistation Access Unit. 2. Hardware or software that is part of a functional unit. computer architecture The organizational structure of a computer system, including hardware and software. (A) configuration 1. The arrangement of a computer system or network as defined by the nature, number, and chief characteristics of its functional units. More specifically, the term may refer to a hardware configuration or a software configuration. (I) (A) 2. The devices and programs that make up a system, subsystem, or network. 3. See also system configuration. ΓòÉΓòÉΓòÉ 28.4. Character D ΓòÉΓòÉΓòÉ data 1. A representation of facts, concepts, or instructions in a formalized manner suitable for communication, interpretation, or processing by human or automatic means. (I) (A) 2. Any representations such as characters or analog quantities to which meaning is or might be assigned. (A) data base A set of data, part or the whole of another set of data, that consists of at least one file, and that is sufficient for a given purpose or for a given data processing system. (I) (A) data link 1. Any physical link, such as a wire or a telephone circuit, that connects one or more remote terminals to a communication control unit, or connects one communication control unit with another. 2. The assembly of parts of two data terminal equipment (DTE) devices that are controlled by a link protocol, and the interconnecting data circuit, that enable data to be transferred from a data source to a data sink. (I) 3. In SNA, see also link. Note: A telecommunication line is only the physical medium of transmission. A data link includes the physical medium of transmission, the protocol, and associated devices and programs; it is both physical and logical. data transfer 1. The result of the transmission of data signals from any data source to a data receiver. 2. The movement, or copying, of data from one location and the storage of the data at another location. debug To detect, diagnose, and eliminate errors in programs. default Pertaining to an attribute, value, or option that is assumed when none is explicitly specified. default value A value assumed when no value has been specified. destination Any point or location, such as a node, station, or particular terminal, to which information is to be sent. device 1. A mechanical, electrical, or electronic contrivance with a specific purpose. 2. An input/output unit such as a terminal, display, or printer. See also attaching device. diagnostics Modules or tests used by computer users and service personnel to diagnose hardware problems. diskette drive The mechanism used to seek, read, and write data on diskettes. Disk Operating System An operating system for computer systems that use disks and diskettes for auxiliary storage of programs and data. ΓòÉΓòÉΓòÉ 28.5. Character E ΓòÉΓòÉΓòÉ emulation 1. The imitation of all or part of one computer system by another, primarily by hardware, so that the imitating system accepts the same data, executes the same programs, and achieves the same results as the imitated computer system. (I) (A) 2. The use of programming techniques and special machine features to permit a computing system to execute programs written for another system. enabled 1. On a LAN, pertaining to an adapter or device that is active, operational, and able to receive frames from the network. 2. Pertaining to a state of a processing unit that allows the occurrence of certain types of interruptions. 3. Pertaining to the state in which a transmission control unit or an audio response unit can accept incoming calls on a line. event An occurrence of significance to a task; for example, the completion of an asynchronous operation, such as an I/O operation. execute To perform the actions specified by a program or a portion of a program. (T) execution The process of carrying out an instruction or instructions of a computer program by a computer. (I) (A) exit To execute an instruction or statement within a portion of a program in order to terminate the execution of that portion. (T) Note: Such portions of programs include loops, routines, subroutines, and modules. expansion slot In an IBM personal computer, one of several receptacles in the system board of the system unit or expansion unit into which a user can install an expansion board such as a memory expansion option. ΓòÉΓòÉΓòÉ 28.6. Character F ΓòÉΓòÉΓòÉ fault An accidental condition that causes a functional unit to fail to perform its required function. (I) (A) feature A part of an IBM product that may be ordered separately by the customer. field On a data medium or a storage medium, a specified area used for a particular category of data; for example, a group of character positions used to enter or display wage rates on a panel. (T) file A named set of records stored or processed as a unit. (T) file name 1. A name assigned or declared for a file. 2. The name used by a program to identify a file. frame 1. The unit of transmission in some LANs, including the IBM Token-Ring Network and the IBM PC Network. It includes delimiters, control characters, information, and checking characters. On a token-ring network, a frame is created from a token when the token has data appended to it. On a token bus network (IBM PC Network), all frames including the token frame contain a preamble, start delimiter, control address, optional data and checking characters, end delimiter, and are followed by a minimum silence period. 2. A housing for machine elements. 3. In synchronous data link control (SDLC), the vehicle for every command, every response, and all information that is transmitted using SDLC procedures. Each frame begins and ends with a flag. function 1. A specific purpose of an entity, or its characteristic action. (A) 2. In data communications, a machine action such as carriage return or line feed. ΓòÉΓòÉΓòÉ 28.7. Character H ΓòÉΓòÉΓòÉ hardware Physical equipment as opposed to programs, procedures, rules, and associated documentation. (I) (A) ΓòÉΓòÉΓòÉ 28.8. Character I ΓòÉΓòÉΓòÉ IBM Personal Computer Disk Operating System (DOS) A disk operating system based on MS-DOS. input/output (I/O) 1. Pertaining to a device whose parts can perform an input process and an output process at the same time. (I) 2. Pertaining to a functional unit or channel involved in an input process, output process, or both, concurrently or not, and to the data involved in such a process. interface 1. A shared boundary between two functional units, defined by functional characteristics, common physical interconnection characteristics, signal characteristics, and other characteristics as appropriate. (I) 2. A shared boundary. An interface may be a hardware component to link two devices or a portion of storage or registers accessed by two or more computer programs. (A) 3. Hardware, software, or both, that links systems, programs, or devices. International Organization for Standardization (ISO) An organization of national standards bodies from various countries established to promote development of standards to facilitate international exchange of goods and services, and develop cooperation in intellectual, scientific, technological, and economic activity. internetwork address The address of a workstation in a Novell NetWare network. The address consists of an optional network number, followed by a required colon and the node address ([network-number]:node-address). interrupt 1. A suspension of a process, such as execution of a computer program, caused by an external event and performed in such a way that the process can be resumed. (A) 2. To stop a process in such a way that it can be resumed. 3. In data communication, to take an action at a receiving station that causes the sending station to end a transmission. 4. A means of passing processing control from one software or microcode module or routine to another, or of requesting a particular software, microcode, or hardware function. ΓòÉΓòÉΓòÉ 28.9. Character L ΓòÉΓòÉΓòÉ LAN adapter The circuit card within a communicating device (such as a personal computer) that, together with its associated software, enables the device to be attached to a LAN. link 1. The logical connection between nodes including the end-to-end link control procedures. 2. The combination of physical media, protocols, and programming that connects devices on a network. 3. In computer programming, the part of a program, in some cases a single instruction or an address, that passes control and parameters between separate portions of the computer program. (I) (A) 4. To interconnect items of data or portions of one or more computer programs. 5. In SNA, the combination of the link connection and link stations joining network nodes. link station 1. A specific place in a service access point (SAP) that enables an adapter to communicate with another adapter. 2. A protocol machine in a node that manages the elements of procedure required for the exchange of data traffic with another communicating link station. 3. A logical point within a SAP that enables an adapter to establish connection-oriented communication with another adapter. 4. In SNA, the combination of hardware and software that allows a node to attach to and provide control for a link. local area network (LAN) A computer network located on a user's premises within a limited geographical area. Note: Communication within a local area network is not subject to external regulations; however, communication across the LAN boundary may be subject to some form of regulation. (T) logical unit (LU) In SNA, a port through which an end user accesses the SNA network in order to communicate with another end user and through which the end user accesses the functions provided by system services control points (SSCPs). An LU can support at least two sessions, one with an SSCP and one with another LU, and may be capable of supporting many sessions with other logical units. ΓòÉΓòÉΓòÉ 28.10. Character M ΓòÉΓòÉΓòÉ medium A physical carrier of electrical or optical energy. medium access control (MAC) protocol In a local area network, the part of the protocol that governs communication on the transmission medium without concern for the physical characteristics of the medium, but taking into account the topological aspects of the network, in order to enable the exchange of data between data stations. (T) megabyte (MB) A unit of measure for data. 1 megabyte = 1 048 576 bytes. message 1. A logical partition of the user device's data stream to and from the adapter. 2. A group of characters and control bits transferred as an entity. Micro Channel The architecture used by IBM Personal System/2 computers, Models 50 and above. This term is used to distinguish these computers from personal computers using a PC I/O channel, such as an IBM PC, XT*, or an IBM Personal System/2 computer, Model 25 or 30. microcode 1. One or more microinstructions. 2. A code, representing the instructions of an instruction set, that is implemented in a part of storage that is not program-addressable. 3. To design, write, and also test one or more microinstructions. modem (modulator/demodulator) A device that converts digital data from a computer to an analog signal that can be transmitted in a telecommunication line, and converts the analog signal received to data for the computer. monitor 1. A functional unit that observes and records selected activities for analysis within a data processing system. Possible uses are to show significant departures from the norm, or to determine levels of utilization of particular functional units. (I) (A) 2. Software or hardware that observes, supervises, controls, or verifies operations of a system. (A) ΓòÉΓòÉΓòÉ 28.11. Character N ΓòÉΓòÉΓòÉ name An alphanumeric term that identifies a data set, statement, program, or cataloged procedure. n-bit byte A string that consists of n bits. (T) NetView A host-based IBM licensed program that provides communication network management (CNM) or communications and systems management (C&SM) services. network 1. A configuration of data processing devices and software connected for information interchange. 2. An arrangement of nodes and connecting branches. Connections are made between data stations. (T) network architecture The logical structure and operating principles of a computer network. (T) See also systems network architecture (SNA) and Open Systems Interconnection (OSI) architecture. Note: The operating principles of a network include those of services, functions, and protocols. Network Basic Input/Output System (NETBIOS) A message interface used on LANs to provide message, print server, and file server functions. The IBM NETBIOS application program interface (API) provides a programming interface to the LAN so that an application program can have LAN communication without knowledge and responsibility of the data link control (DLC) interface. network management The conceptual control element of a station that interfaces with all of the architectural layers of that station and is responsible for the resetting and setting of control parameters, obtaining reports of error conditions, and determining if the station should be connected to or disconnected from the network. network management vector transport The portion of an alert transport frame that contains the alert message. network manager A program or group of programs that is used to monitor, manage, and diagnose the problems of a network. node 1. Any device, attached to a network, that transmits and/or receives data. 2. An end point of a link, or a junction common to two or more links in a network. 3. In a network, a point where one or more functional units interconnect transmission lines. node address The address of an adapter on a LAN. ΓòÉΓòÉΓòÉ 28.12. Character O ΓòÉΓòÉΓòÉ open 1. To make an adapter ready for use. 2. A break in an electrical circuit. 3. To make a file ready for use. Open Systems Interconnection (OSI) 1. The interconnection of open systems in accordance with specific ISO standards. (T) 2. The use of standardized procedures to enable the interconnection of data processing systems. Note: OSI architecture establishes a framework for coordinating the development of current and future standards for the interconnection of computer systems. Network functions are divided into seven layers. Each layer represents a group of related data processing and communication functions that can be carried out in a standard way to support different applications. Open Systems Interconnection (OSI) architecture Network architecture that adheres to a particular set of ISO standards that relates to Open Systems Interconnection. (T) Open Systems Interconnection (OSI) reference model A model that represents the hierarchical arrangement of the seven layers described by the Open Systems Interconnection architecture. operating system Software that controls the execution of programs. An operating system may provide services such as resource allocation, scheduling, input/output control, and data management. (A) Examples are IBM PC DOS and IBM OS/2. Operating System/2 (OS/2) A set of programs that control the operation of high-speed large-memory IBM personal computers (such as the IBM Personal System/2 computer, Models 50 and above), providing multitasking and the ability to address up to 16 MB of memory. Contrast with Disk Operating System (DOS). operation 1. A defined action, namely, the act of obtaining a result from one or more operands in accordance with a rule that completely specifies the result for any permissible combination of operands. (A) 2. A program step undertaken or executed by a computer. 3. An action performed on one or more data items, such as adding, multiplying, comparing, or moving. option 1. A specification in a statement, a selection from a menu, or a setting of a switch, that may be used to influence the execution of a program. 2. A hardware or software function that may be selected or enabled as part of a configuration process. 3. A piece of hardware (such as a network adapter) that can be installed in a device to modify or enhance device function. output device A device in a data processing system by which data can be received from the system. (I) (A) Synonymous with output unit. output unit Synonym for output device. ΓòÉΓòÉΓòÉ 28.13. Character P ΓòÉΓòÉΓòÉ packet 1. In data communication, a sequence of binary digits, including data and control signals, that is transmitted and switched as a composite whole. (I) 2. Synonymous with data frame. Contrast with frame. panel The complete set of formatted information that appears in a single display on a visual display unit. parameter 1. A variable that is given a constant value for a specified application and that may denote the application. (I) (A) 2. An item in a menu or for which the user specifies a value or for which the system provides a value when the menu is interpreted. 3. Data passed between programs or procedures. path 1. In a network, any route between any two nodes. (T) 2. The route traversed by the information exchanged between two attaching devices in a network. 3. A command in IBM Personal Computer Disk Operating System (PC DOS) and IBM Operating System/2 (OS/2) that specifies directories to be searched for commands or batch files that are not found by a search of the current directory. personal computer (PC) A desk-top, free-standing, or portable microcomputer that usually consists of a system unit, a display, a monitor, a keyboard, one or more diskette drives, internal fixed-disk storage, and an optional printer. PCs are designed primarily to give independent computing power to a single user and are inexpensively priced for purchase by individuals or small businesses. Examples include the various models of the IBM Personal Computers, and the IBM Personal System/2 computer. physical unit (PU) In SNA, the component that manages and monitors the resources of a node, such as attached links and adjacent link stations, as requested by a system services control point (SSCP) via an SSCP-SSCP session. pointer 1. An identifier that indicates the location of an item of data. (A) 2. A data element that indicates the location of another data element. (T) 3. A physical or symbolic identifier of a unique target. procedure A set of instructions that gives a service representative a step-by-step procedure for tracing a symptom to the cause of failure. processor In a computer, a functional unit that interprets and executes instructions. (I) (A) protocol 1. A set of semantic and syntactic rules that determines the behavior of functional units in achieving communication. (I) 2. In SNA, the meanings of and the sequencing rules for requests and responses used for managing the network, transferring data, and synchronizing the states of network components. 3. A specification for the format and relative timing of information exchanged between communicating parties. ΓòÉΓòÉΓòÉ 28.14. Character R ΓòÉΓòÉΓòÉ random access memory (RAM) A computer's or adapter's volatile storage area into which data may be entered and retrieved in a nonsequential manner. receive To obtain and store information transmitted from a device. return code 1. A value (usually hexadecimal) provided by an adapter or a program to indicate the result of an action, command, or operation. 2. A code used to influence the execution of succeeding instructions. (A) ring network A network configuration in which a series of attaching devices is connected by unidirectional transmission links to form a closed path. A ring of an IBM Token-Ring Network is referred to as a LAN segment or as a Token-Ring Network segment. ring segment A ring segment is any section of a ring that can be isolated (by unplugging connectors) from the rest of the ring. A segment can consist of a single lobe, the cable between access units, or a combination of cables, lobes, and/or access units. routing 1. The assignment of the path by which a message will reach its destination. 2. The forwarding of a message unit along a particular path through a network, as determined by the parameters carried in the message unit, such as the destination network address in a transmission header. ΓòÉΓòÉΓòÉ 28.15. Character S ΓòÉΓòÉΓòÉ scroll To move all or part of the display image vertically or horizontally to display data that cannot be observed within a single display image. See also page (2). server 1. A device, program, or code module on a network dedicated to providing a specific service to a network. 2. On a LAN, a data station that provides facilities to other data stations. Examples are a file server, print server, and mail server. service access point (SAP) 1. A logical point made available by an adapter where information can be received and transmitted. A single SAP can have many links terminating in it. 2. In Open Systems Interconnection (OSI) architecture, the logical point at which an n + 1-layer entity acquires the services of the n-layer. For LANs, the n-layer is assumed to be data link control (DLC). A single SAP can have many links terminating in it. These link "end-points" are represented in DLC by link stations. session 1. A connection between two application programs that allows them to communicate. 2. In SNA, a logical connection between two network addressable units that can be activated, tailored to provide various protocols, and deactivated as requested. 3. The data transport connection resulting from a call or link between two devices. 4. The period of time during which a user of a node can communicate with an interactive system, usually the elapsed time between log on and log off. 5. In network architecture, an association of facilities necessary for establishing, maintaining, and releasing connections for communication between stations. (T) station 1. A communication device attached to a network. The term used most often in LANs is an attaching device or workstation. 2. An input or output point of a system that uses telecommunication facilities; for example, one or more systems, computers, terminals, devices, and associated programs at a particular location that can send or receive data over a telecommunication line. See also attaching device, workstation. subvector A subcomponent of the medium access control (MAC) major vector. synchronous 1. Pertaining to two or more processes that depend on the occurrences of a specific event such as common timing signal. (I) (A) 2. Occurring with a regular or predictable timing relationship. synchronous data link control (SDLC) A discipline conforming to subsets of the Advanced Data Communication Control Procedures (ADCCP) of the American National Standards Institute (ANSI) and High-level Data Link Control (HDLC) of the International Organization for Standardization, for managing synchronous, code-transparent, serial-by-bit information transfer over a link connection. Transmission exchanges may be duplex or half-duplex over switched or nonswitched links. The configuration of the link connection may be point-to-point, multipoint, or loop. (I) system In data processing, a collection of people, machines, and methods organized to accomplish a set of specific functions . (I) (A) system configuration A process that specifies the devices and programs that form a particular data processing system. Systems Application Architecture (SAA) An architecture developed by IBM that consists of a set of selected software interfaces, conventions, and protocols, and that serves as a common framework for application development, portability, and use across different IBM hardware systems. Systems Network Architecture (SNA) The description of the logical structure, formats, protocols, and operational sequences for transmitting information units through, and controlling the configuration and operation of, networks. ultimate origins and destinations of information, that is, the end users, to be independent of and unaffected by the specific SNA network services and facilities used for information exchange. ΓòÉΓòÉΓòÉ 28.16. Character T ΓòÉΓòÉΓòÉ text editor A program used to create, modify, and print or display text files. threshold 1. A level, point, or value above which something is true or will take place and below which it is not true or will not take place. 2. In IBM bridge programs, a value set for the maximum number of frames that are not forwarded across a bridge due to errors, before a "threshold exceeded" occurrence is counted and indicated to network management programs. 3. An initial value from which a counter is decremented to zero, or a value to which a counter is incremented or decremented from an initial value. When the counter reaches zero or the threshold value, a decision is made and/or an event occurs. token A sequence of bits passed from one device to another on the token-ring network that signifies permission to transmit over the network. It consists of a starting delimiter, an access control field, and an end delimiter. The access control field contains a bit that indicates to a receiving device that the token is ready to accept information. If a device has data to send along the network, it appends the data to the token. When data is appended, the token then becomes a frame. See frame. token ring A network with a ring topology that passes tokens from one attaching device (node) to another. A node that is ready to send can capture a token and insert data for transmission. token-ring network 1. A ring network that allows unidirectional data transmission between data stations by a token-passing procedure over one transmission medium so that the transmitted data returns to and is removed by the transmitting station. (T) The IBM Token-Ring Network is a baseband LAN with a star-wired ring topology that passes tokens from network adapter to network adapter. 2. A network that uses a ring topology, in which tokens are passed in a sequence from node to node. A node that is ready to send can capture the token and insert data for transmission. 3. A group of interconnected token rings. trace 1. A record of the execution of a computer program. It exhibits the sequences in which the instructions were executed. 2. A record of the frames and bytes transmitted on a network. transmit To send information from one place for reception elsewhere. ΓòÉΓòÉΓòÉ 28.17. Character U ΓòÉΓòÉΓòÉ uninterruptible power supply (UPS) A buffer between utility power or other power source and a load that requires uninterrupted, precise power. It is usually battery powered. usability The quality of a system, program, or device that enables it to be easily understood and conveniently employed by a user. ΓòÉΓòÉΓòÉ 28.18. Character V ΓòÉΓòÉΓòÉ variable 1. In computer programming, a character or group of characters that refers to a value and, in the execution of a computer program, corresponds to an address. 2. A quantity that can assume any of a given set of values. (A) vector One or more related fields of data, in a specified format. A quantity usually characterized by an ordered set of numbers. (I) (A) ΓòÉΓòÉΓòÉ 28.19. Character W ΓòÉΓòÉΓòÉ wide area network (WAN) A network that provides data communication capability in geographic areas larger than those serviced by LANs. workstation 1. An I/O device that allows either transmission of data or the reception of data (or both) from a host system, as needed to perform a job: for example, a display station or printer. 2. A configuration of I/O equipment at which an operator works. (T) 3. A terminal or microcomputer, usually one connected to a mainframe or network, at which a user can perform tasks. ΓòÉΓòÉΓòÉ 29. Reader's Comment Form ΓòÉΓòÉΓòÉ LAN Management Utilities User's Guide PRPQ P85220 Publication No. SC30-3555-02 Use this form to tell us what you think about this manual. If you have found errors in it, or if you want to express your opinion about it (such as organization, subject matter, appearance) or make suggestions for improvement, this is the form to use. To request additional publications, or to ask questions or make comments about the functions of IBM products or systems, you should talk to your IBM representative or to your IBM authorized remarketer. This form is provided for comments about the information in this manual and the way it is presented. When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. Address your comments to: IBM Corporation Department E02 P.O. Box 12195 Research Triangle Park, North Carolina 27709-9990 U.S.A. Be sure to print your name and address below if you would like a reply. Name__________________________________ Address_______________________________ Company or Organization__________________________ _______________________________ Phone No._____________________________ _______________________________